Closed
Bug 1055709
Opened 9 years ago
Closed 9 years ago
e10s: Automatic redirects to HTTPS don't work
Categories
(Core :: Networking, defect, P1)
Tracking
()
RESOLVED
DUPLICATE
of bug 946739
People
(Reporter: sstangl, Unassigned)
References
()
Details
Without e10s, visiting "http://www.cmubash.org" automatically redirects to "https://www.cmubash.org". With e10s, visiting "http://www.cmubash.org" displays a document with the text content "Found: The document has moved here (https://cmubash.org)".
![]() |
||
Comment 1•9 years ago
|
||
This is an HTTP 302. Looks like it's not getting processed for some reason and showing the response body instead?
Component: General → Networking
![]() |
||
Updated•9 years ago
|
Updated•9 years ago
|
Blocks: e10s-necko
Comment 2•9 years ago
|
||
Sean: do you have any networking-releated add-ons installed, such as HTTPS Everywhere or RequestPolicy? I can't reproduce this bug with a clean profile. There are known issues (bug 946739) with HTTPS Everywhere breaking redirects.
Flags: needinfo?(sstangl)
See Also: → 946739
Reporter | ||
Comment 3•9 years ago
|
||
Disabling HTTPS Everywhere allows the redirects to work, so it's probably a dup of Bug 945739.
Flags: needinfo?(sstangl)
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•9 years ago
|
No longer blocks: e10s-necko, old-e10s-m2
tracking-e10s:
+ → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•