I am running latest MacOS Sequoia 15.3.1 and latest Apps and have noticed this behavior at least since 15.2, perhaps much longer.
There is one URL (local library) that sometimes can easily be accessed from Google Chrome but not from Safari.
Once it will connect with Safari I have no further issues getting to it until perhaps the next day.
My configuration uses DHCP with Manual Address and I have different IP addresses assigned to the Ethernet and WiFi interfaces.
Today, I discovered that when this URL is unreachable from Safari, but working normally from Chrome, that I now reach from Safari if I turn off WiFi. It does not seem to make logical sense to me, but the behavior seems to be that Safari uses TCP/IP in a way differently from Chrome so that Chrome will function when this happens and Safari will not.
So, as a user, if you find a URL that will not connect from Safari but will from another browser, see if making sure you have just one interface active heals the problem.
I am not 100% certain this is not just chance, as it is based upon the one observation today.
Perhaps it could happen with Chrome failing and Safari working, or just maybe that Safari is sensitive to physical interface. (if command/response used different interfaces)
There is one URL (local library) that sometimes can easily be accessed from Google Chrome but not from Safari.
Once it will connect with Safari I have no further issues getting to it until perhaps the next day.
My configuration uses DHCP with Manual Address and I have different IP addresses assigned to the Ethernet and WiFi interfaces.
Today, I discovered that when this URL is unreachable from Safari, but working normally from Chrome, that I now reach from Safari if I turn off WiFi. It does not seem to make logical sense to me, but the behavior seems to be that Safari uses TCP/IP in a way differently from Chrome so that Chrome will function when this happens and Safari will not.
So, as a user, if you find a URL that will not connect from Safari but will from another browser, see if making sure you have just one interface active heals the problem.
I am not 100% certain this is not just chance, as it is based upon the one observation today.
Perhaps it could happen with Chrome failing and Safari working, or just maybe that Safari is sensitive to physical interface. (if command/response used different interfaces)
