Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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!