News for hackers. Stuff that matters.

A comment on Service provider story about tracking down TCP RSTs. Parent comment

Re:Service provider story about tracking down TCP RSTs by londons_explore on Sunday September 02, 2018 @09:24AM (#17896918)
>It's generally deemed 'acceptable' in Anycast terms to cause a TCP RST when traffic switches from one POP to another...

>For things like websites, browsers will usually just retry the connection

This is not the case. Every single TCP RST you send on an active http connection will lead to an http request failing in a way which causes application brokenness. No browser auto-retries in that case. The user always has to hit refresh to fix it.

[ Parent | on HN ]
Re:Service provider story about tracking down TCP RSTs by cnst on Monday September 03, 2018 @02:21AM (#17900734)
At least with the TCP RST it'll fail fast. What's annoying is that some providers decide that you aren't worthy of the RST; then your browser has to wait for like 3 minutes until the timeout is reached — really annoying.
[ Parent | on HN ]