Open Bug 1547556 Opened 2 years ago Updated 2 years ago

Support flagging a temporary redirect has occurred in xmlhttprequest

Categories

(Core :: DOM: Networking, enhancement, P3)

65 Branch
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: thosrtanner58, Unassigned)

References

()

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.9) Gecko/20100101 Goanna/4.1 Firefox/60.9 PaleMoon/28.4.1

Steps to reproduce:

As per https://github.com/whatwg/fetch/issues/892 there currently is no way of determining if the url you get as the target url after an xmlhttprequest is resolved was changed as the result of a temporary request (and therefore would not be a good idea to store/save) or not.

Would it be possible to implement this change please?

Actual results:

For instance going here: https://status.secondlifegrid.net/feed gets a 302 redirect to https://status.secondlifegrid.net/history.atom. However this is a temporary redirection and really should be flagged as such (I've been able to find any other long lasting temporary redirects!)

Expected results:

I'd have like a flag in the XMLHttpRequest indicating that the final target had been the result of a temporary redirection.

Sorry, reporting this on wrong browser. User agent string should read:

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

Type: defect → enhancement
OS: Unspecified → All
Hardware: Unspecified → All
Version: 68 Branch → 65 Branch
Component: Untriaged → DOM: Networking
Product: Firefox → Core
Summary: I'd like to request an enhacement to firefox to support flagging a temporary redirect has occurred in xmlhttprequest → Support flagging a temporary redirect has occurred in xmlhttprequest

We can leave this open I suppose, but we shouldn't really do any work until the standardization discussion Gingerbread Man has helpfully linked to has concluded, unless we're really keen on pushing this for some reason.

If you mean this: https://github.com/whatwg/fetch/issues/892 - I raised this ticket as a result of that being set to 'needs implementer interest'. This seemed a good place to raise implementer interest.

Priority: -- → P3
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.