לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

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

  • 3 תגובות
  • 1 has this problem
  • 2 views
  • תגובה אחרונה מאת aprilmp

more options

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.

כל התגובות (3)

more options

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.

more options

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
more options

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.