Re: [whatwg/fetch] Remove Authorization header upon cross-origin redirect (PR #1544) from Sachin Jain on 2023-11-08 (public-webapps-github@w3.org from November 2023)

From: Sachin Jain <notifications@github.com>
Date: Wed, 08 Nov 2023 05:57:20 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/pull/1544/c1801942061@github.com>

@annevk This change has been rolled out in Chrome v119 (Refer to [release notes](https://support.google.com/chrome/a/answer/7679408?sjid=2334110632176692414-AP#chromeBrsrK119) here).

This has broken the development setup, which used Fetch redirects from Staging/API endpoints to the localhost server. 

Is there a way to configure the browser to still pass the auth header for a list of specified domains? or pass auth header to localhost, 127.0.0.1, 0.0.0.0, etc domains?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1544#issuecomment-1801942061
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1544/c1801942061@github.com>

Received on Wednesday, 8 November 2023 13:57:26 UTC