Closed Bug 1522940 Opened 6 years ago Closed 6 years ago

When we're told to not follow redirects, we shouldn't try to follow them

Categories

(Core :: Networking: HTTP, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox66 --- wontfix
firefox67 --- fixed

People

(Reporter: bzbarsky, Assigned: bzbarsky)

References

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

Right now we check the loadinfo's "don't follow redirects" flag way late into the redirect processing pipeline, after we have done a bunch of work (and possibly failed the load, e.g. due to a malformed Location header).

We should be checking it much earlier, I would think.

Priority: -- → P1
Whiteboard: [necko-triaged]
Pushed by bzbarsky@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2d821bddaa20 Bail out of redirect processing immediately if our loadinfo says to not follow redirects. r=mayhemer
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67

Given where we are in the cycle, is this something we should consider uplifting to Beta or can it ride the trains?

Flags: needinfo?(bzbarsky)

I think it's fine for this to ride the trains. It's not a new problem, it only affects certain very specific uses of the fetch API, and it hasn't seemed to be a problem in the wild so far.

Flags: needinfo?(bzbarsky)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: