| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| | |
|
| |
|
|
| |
Another S&R run with some smarter matching.
|
| |
|
|
|
|
| |
Since these are just interpreted comments, there's 0 impact on actual code.
This removes all lines that match /* vim: set(.*)tw=80: */ with S&R -- there are
a few others scattered around which will be removed manually in a second part.
|
| | |
|
| | |
|
| |
|
|
| |
Tag #993.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
origins
Potential attack: session supercookie.
[Moz Notes](https://bugzilla.mozilla.org/show_bug.cgi?id=1334776#c5):
"The problem is that for unknown header names we store the first one we see and then later we case-insensitively match against that name *globally*. That means you can track if a user agent has already seen a certain header name used (by using a different casing and observing whether it gets normalized). This would allow you to see if a user has used a sensitive service that uses custom header names, or allows you to track a user across sites, by teaching the browser about a certain header case once and then observing if different casings get normalized to that.
What we should do instead is only store the casing for a header name for each header list and not globally. That way it only leaks where it's expected (and necessary) to leak."
[Moz fix note](https://bugzilla.mozilla.org/show_bug.cgi?id=1334776#c8):
"nsHttpAtom now holds the old nsHttpAtom and a string that is case sensitive (only for not standard headers).
So nsHttpAtom holds a pointer to a header name. (header names are store on a static structure). This is how it used to be. I left that part the same but added a nsCString which holds a string that was used to resoled the header name. So when we parse headers we call ResolveHeader with a char*. If it is a new header name the char* will be stored in a HttpHeapAtom, nsHttpAtom::_val will point to HttpHeapAtom::value and the same strings will be stored in mLocalCaseSensitiveHeader. For the first resolve request they will be the same but for the following maybe not. At the end this nsHttpAtom will be stored in nsHttpHeaderArray. For all operation we will used the old char* except when we are returning it to a script using VisitHeaders."
|
| |
|
|
| |
This resolves #738
|
| |
|
|
|
|
| |
Also add test for faulty nsStandardURL deserialization.
See Bug 1392739.
|
| | |
|
| |\
| |
| | |
moebius#131: URL parser - stop preserving empty passwords
|
| | |
| |
| |
| | |
https://github.com/MoonchildProductions/moebius/issues/131
|
| |\|
| |
| | |
moebius#130: URL parser - fix: don't allow empty host name
|
| | |
| |
| |
| | |
https://github.com/MoonchildProductions/moebius/issues/130
|
| |\ \
| |/
|/| |
Fix: no escape single quote in location.hash
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
