We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

For some websites, why does Firefox send multiple of the same http GET requests?

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 2 views
  • Last reply by aprilmp

The requests can't be seen in Firebug, but you can see them in Tamper Data or any other tool that monitors requests. They only happen with GETs that have a response code of 200. They only happen for some web applications.

If in config I I set the max-persistent-connections-per-server to 1, then the issue does not happen.

If in config I set the max-persistent-connections-per-server to 6, then Firefox sends out three extra requests per http-GET.

The requests can't be seen in Firebug, but you can see them in Tamper Data or any other tool that monitors requests. They only happen with GETs that have a response code of 200. They only happen for some web applications. If in config I I set the max-persistent-connections-per-server to 1, then the issue does not happen. If in config I set the max-persistent-connections-per-server to 6, then Firefox sends out three extra requests per http-GET.

All Replies (3)

Updated: if I turn caching on (I had it disabled), then the 4th of the 4 requests is retrieved from the cache. The other 3 seem to still go to the server, though.

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window

I tried this out, and in safe mode with the default theme, the issue still occurs.

To clarify, my browser doesn't do this with all sites. It does it with just this one web app (that I've observed) and I'm trying to figure out what it is about these requests/responses that would trigger this behavior.