@aral this wording mentioning 'receiver' makes me feel like a Proxy instance was involved, but they're not really used much outside testing frameworks I think :P
Notices by Daniel (dan@freeradical.zone)
-
Daniel (dan@freeradical.zone)'s status on Monday, 22-May-2023 18:31:06 JST Daniel -
Daniel (dan@freeradical.zone)'s status on Saturday, 11-Feb-2023 03:16:18 JST Daniel @aral glad I could help :)
On the topic of TLS I was about to suggest a wildcard certificate `*.localhost` but it turns out that's not allowed by browsers 😅 via https://stackoverflow.com/a/68514822/3582903 -
Daniel (dan@freeradical.zone)'s status on Friday, 10-Feb-2023 21:08:36 JST Daniel @aral There's also subdomains of localhost e.g. instance1.localhost
& instance2.localhost. I'm not sure if Firefox implements that, but Chrome will always resolve subdomains of localhost to localhost.
You could also run a proxy (caddy, nginx, etc) on 443 and have it send the different subdomains/IPs to the different instances.
Yea, cookies are effectively just host+path :)