@konnorrogers It also works in Firefox on Windows. So the issue seems to be that: Safari uses the system DNS resolution, the system DNS resolution doesn't resolve subdomains of localhost, and Safari doesn't include special handling to overcome that fact.
I'm being slightly pedantic on purpose. Because if the system DNS doesn't resolve "whatever.localhost" correctly, there'll be unexpected results when developing non-web services. E.g. if you're building or using an FTP server on "myfpt.localhost", clients won't be able to connect to it unless they include the same workaround as Chrome and Firefox.
TL;DR: the system DNS resolution should probably be better, and no browser should need to implement special handling. @mahryekuh
=> More informations about this toot | View the thread | More toots from jscholes@dragonscave.space
=> View konnorrogers@ruby.social profile | View mahryekuh@fosstodon.org profile
text/geminiThis content has been proxied by September (3851b).