본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

HTTP request (GET) executed twice after RST TCP

  • 3 답장
  • 1 이 문제를 만남
  • 10 보기
  • 최종 답변자: afcinza

more options

I have a load balancer that is executing a reset in the TCP connections when I try to execute a PHP script which takes a long time to finish (400 sec). We are debugging this but the problem is that, when Firefox receives the RST, it executes the same query again. This can generate big problems. You can see the problem in the next Wireshark screenshot. Any idea about why Firefox is doing this?

Thank you in advance. Regards.

I have a load balancer that is executing a reset in the TCP connections when I try to execute a PHP script which takes a long time to finish (400 sec). We are debugging this but the problem is that, when Firefox receives the RST, it executes the same query again. This can generate big problems. You can see the problem in the next Wireshark screenshot. Any idea about why Firefox is doing this? Thank you in advance. Regards.

모든 댓글 (3)

more options

I attach the Wireshark screenshot. Thanks!

more options

See:

HTTP connections now have a response timeout

If your application is processing large data and affected by this change, you can change the value of the network.http.response.timeout preference to a larger number via about:config.

  • Bug 947391 – HTTP connections (exc. XHR, SPDY) should have a response timeout
more options

Thank you for your quick answer, cor-el. I knew about this parameter but the main problem is the second GET that Firefox executes automatically after receiving the TCP RST. The browser should not execute a second GET without user control, shouldn't it? This is strange but this behaviour is reproducible.

The PHP scripts execute some changes into a database. If the browser executes the HTTP request without user control this may produce an unexpected result.

Thank you!