| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
This reverts commit 18df01eb5498c954044f96c346026da0238d2e61.
Backed out for devtools breakage.
|
|
|
|
| |
Resolves #1684
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Since we're needing to reuse this several times, it makes it simpler to
just get it once in init and storing it.
|
|
|
|
|
|
|
| |
To respond dynamically to the pref change, the mAppVersion string needs
to be rebuilt.
Includes some minor improvements for corner cases and removes leftover
b2g junk.
|
| |
|
| |
|
| |
|
|
|
|
| |
`UserAgentUpdates.jsm`
|
| |
|
|
|
|
| |
netwerk/protocol/http/nsHttpHandler.cpp
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This reverts commit 67d336a6f27889bdef4723194b6611d049830266.
|
| |
|
| |
|
|
|
|
| |
Fixes a regression in Part 1b which caused HTML5 parser to fall off the main thread.
|
|
|
|
|
|
| |
and AutomaticAuth, and default to not prompting.
This resolves #1275.
|
| |
|
|
|
|
|
|
| |
along with it (1445670 and 1373780 part 2 and 3)
Convert dom/base/nsImageLoadingContent.cpp to use AsyncOpen2 and followups along with it (1445670 and 1373780 part 2 and 3)
|
|
|
|
| |
This re-applies the patch for this with added typename declaration.
|
|
|
|
|
|
| |
Backed out because of gcc build failures.
This reverts commit 66fae1d81013a2321e7d607a426f834a01b847ce.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Still allow this to be bypassed with a pref for those really rare corner
cases where images are loaded cross-origin by design and the session
hasn't been/can't be authenticated ahead of time.
|
|
|
|
| |
tunnel.
|
|
|
|
|
|
| |
When PR_Read/PR_White returns -1, we have to use ErrorAccordingToNSPR
to get the error code.
We need to close the transaction if a real error happens.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Defaults to false if not configured.
|
|
|
|
|
|
| |
Apparently there is some functional and naming confusion here.
Backing out to re-land after evaluation and possible changes.
Tag #863.
|
|
|
|
|
|
|
| |
This adds a pref "network.http.opportunistic-encryption" that controls whether
we send an "Upgrade-Insecure-Requests : 1" header on document navigation or not.
This patch modifies the platform network parts. Default for the platform is "true".
Part 1 for #863
|
| |
|
|\
| |
| | |
Issue #792 - backport mozbug 1334776 - CVE-2017-7797 Header name interning leaks across origins
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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."
|
|/
|
|
|
|
|
|
| |
r=mayhemer
The original code (from bug 1200802) declared an XPCOM object as a static bare pointer,
which for future reference is probably never the right thing to do. It might have worked if
it was cleared before shutdown but it never was.
|