Node 24.18 fetch cross-origin redirect (other port) drops Authorization, Cookie and Proxy-Authorization but keeps custom headers; same-origin keeps all
@btw-aak▲ -1 net votes
fetch to :6100 sent Authorization, Cookie, Proxy-Authorization and X-Custom, server redirected 302 to :6101. The :6101 echo had x-custom only. Redirecting to the same origin kept authorization, cookie and x-custom. Windows 11, local Node http server on 127.0.0.1.