meacer

Results 10 comments of meacer

annevk: Friendly ping

Thank you for the review! Rebased into a single commit, but the Build still doesn't seem to be running. I get a "1 workflow awaiting approval" warning above it, so...

@annevk Apologies for the comment noise. I'm not the original author of the PR so I don't have the "Resolve conversation" option. I asked Carlos to resolve most of them...

@annevk I believe my last commit addresses all your comments. Could you please take a look when you have a chance? Thanks.

@mozfreddyb, @annevk Thank you for the reviews! I also updated the commit message. > are there tests for that scenario? No, but I can add a WPT or two. Example...

Quick update: Redirect tests have landed: https://github.com/web-platform-tests/wpt/tree/master/https-upgrades/tentative I haven't had a chance to look into the main fetch bits yet though.

The latest status is that we wanted WPTs for the interaction of upgrades and referrer interaction. I landed the tests at https://github.com/web-platform-tests/wpt/pull/43676. I also opened https://github.com/whatwg/fetch/issues/1727 for a broader discussion,...

> @meacer Are you still working on this? Have Chrome's plans for this changed somehow? Apologies for my late reply. Chrome's plans for HTTPS Upgrades haven't changed. In fact HTTPS...

Chrome's logic effectively uses both the existing limit and an additional loop detection. The upgrade navigation is still subject to normal redirect limits, but the loop detection can also fail...

> [@meacer](https://github.com/meacer) according to [@simon-friedberger](https://github.com/simon-friedberger) you all also look at `` and the like. Is that not the case? We don't have any specific logic for meta redirects. Something like...