Frederik Braun
Frederik Braun
@stackmystack Please take a look at some of the suggested changes. We can easily wait ~5 more weeks :)
Looks like everything works as intended here. We can repurpose the issue, if someone wants to update the documentation though.
This is already part of the HTML spec. All browser engines have committed to implement this. * Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1478969 * Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1851575 * WebKit: https://bugs.webkit.org/show_bug.cgi?id=261143
This also shipped in Firefox 122.
I noticed that some redirects are implicitly addressed by virtue of layering the algorithm relatively high in the calling chain. Not sure if it's too verbose to address this explicitly...
> @mozfreddyb you mentioned redirects a few times. Could you stipulate the concern more clearly? Mostly that if you have HTTPS A redirecting to HTTP B we'd attempt an upgrade...
What's the status of this pull request?
I believe there is a disconnect about the redirect loops between what @annevk and @simon-friedberger understood. The issue isn't reaching the maximum of allowed redirects, but whether a browser should...
@meacer Are you still working on this? Have Chrome's plans for this changed somehow?