Nope. Just hooked my other laptop up to my 5G hotspot and am getting the same behaviour: works with firefox, hangs with wget and 403's with chrome. So I don't think it's on my side of the network and I'm getting the same behaviour on chrome on my android device. It's easy enough to install firefox for android, maybe I'll try it there.
So... since it works with firefox and it works for other people, it's probably not opentable's website. Though maybe there's a middlebox somewhere looking at UA headers? But that's crazy talk.
And I logged into a different chrome account and my default account has no apps / extensions loaded.
Funky.
Oh wait. I turned DNS over HTTPS on in firefox to test it out a few weeks ago. Turned it off and no... still working. Was thinking it might have been a DNS thing.
Funky. Works fine on Firefox, just borked on Chrome.
So maybe this should be "Ask HN: Why does https://www.opentable.com/ work on Firefox, but gives me a 403 on chrome and hang when I try to connect with wget?"
Interesting. Sending a request using PowerShell's Invoke-WebRequest results in the request simply hanging. I'm using Fiddler as a proxy.
GET https://www.opentable.com/ HTTP/1.1
Host: www.opentable.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Microsoft Windows 10.0.19045; en-US) PowerShell/7.2.7
Invoking the request from Firefox works fine.
Definitely looks like some kind of TLS termination/proxy/load balancer problem.
Hey. Can you reach pubmed.ncbi.nlm.nih.gov? I'm getting a similar problem. Works on firefox, doesn't work in chrome, hangs when I try to connect with `openssl s_client -connect pubmed.ncbi.nlm.nih.gov:443 -servername pubmed.ncbi.nlm.nih.gov` on a recent ubuntu distro.
Did we change TCP/IP while I wasn't looking? More likely there's a middlebox implementing a TCP shibboleth the firefox guys know about but the chrome team hasn't implemented yet. Or maybe it's just leenucks is doing something funky and somehow firefox knows how to avoid leenucks funkiness.
6 comments
[ 3.3 ms ] story [ 28.9 ms ] threadSo... since it works with firefox and it works for other people, it's probably not opentable's website. Though maybe there's a middlebox somewhere looking at UA headers? But that's crazy talk.
And I logged into a different chrome account and my default account has no apps / extensions loaded.
Funky.
Oh wait. I turned DNS over HTTPS on in firefox to test it out a few weeks ago. Turned it off and no... still working. Was thinking it might have been a DNS thing.
So maybe this should be "Ask HN: Why does https://www.opentable.com/ work on Firefox, but gives me a 403 on chrome and hang when I try to connect with wget?"
Modernity is weird.
Definitely looks like some kind of TLS termination/proxy/load balancer problem.
Did we change TCP/IP while I wasn't looking? More likely there's a middlebox implementing a TCP shibboleth the firefox guys know about but the chrome team hasn't implemented yet. Or maybe it's just leenucks is doing something funky and somehow firefox knows how to avoid leenucks funkiness.