Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

HTTP request (GET) executed twice after RST TCP

  • 3 fhreagra
  • 1 leis an bhfadhb seo
  • 10 views
  • Freagra is déanaí ó afcinza

afcinza
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.

All Replies (3)

afcinza
afcinza Úinéir na ceiste
more options

I attach the Wireshark screenshot. Thanks!

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
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
afcinza
afcinza Úinéir na ceiste
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!