1142000 - Firefox 36.0.x do not support HTTP 302 redirects and shows "document moved"

Status: RESOLVED INCOMPLETE

(Core :: General, defect)

Description

[roberto.cisternino]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150305021524

Steps to reproduce:

I generate server-side a HTTP 302 redirect either in the same domain or external domains. Since Firefox 35.0.x the browser obtains the following response:

"Document moved
This document has moved here."

By inspecting Firefox logs I also find
"Blocked loading mixed active content"




Actual results:

Redirects to http from an https are forbidden even on different domains.
This is acceptable while navigating on facebook or similar untrusted sites, but using an Extranet it should be allowed to use any redirect generated by the server.


Expected results:

A user logged on a Extranet portal should be able to use any service provided by the portal including redirects. Redirects are done due to change of context, domain or other reasons that should not be limited by the browser all the times.
Redirect are a *well* known instrument to avoid keeping a cache on the browser (to limit the back function) as a copletely new request is done.
In a modern browser I would expect two Buttons on top of the browser relatid to the navigation context: Internet (medium trust if user is logged on), Extranet (full trust when user is logged on).  This could be a better handling of this security issue.
Passive/Active mixed content do not means itself so much, it depends where this happen !

Comment 1

[Nickolay_Ponomarev]

I can't find references to 
> "Document moved
> This document has moved here."
...in the source code.

It's also not very clear what situation you're describing. A clearer description would go something like this:
1. User goes to https://mysite.com/
2. The server responds with 302 redirect to http://mysite.com/
3. Instead of loading http://mysite.com/ Firefox displays (screenshot)

It's probable that whatever change you're talking about was intentional, but I can't even find it...

Comment 2

[Simona Badau, Desktop QA]

Based of lack of additional information from the reporter this bug will have the Status: Resolved as incomplete.

@reporter: if you still have the problem reproducible (preferably on the latest stable release) please do not hesitate to reopen the issue while providing additional details that could help us reproduce or identify your issue.

Comment 3

[Firefox Bug Husbandry Bot]

Moving from Core::Untriaged to Core::General https://bugzilla.mozilla.org/show_bug.cgi?id=1407598