Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

What would cause Firefox to request a resource multiple times after a long running script?

krevels
krevels
more options

I'm noticing some unusual behavior in Firefox when I include an image directly after a call to an external script which is long-running.

For example: 

    <html>
    <body>
    
    <script type="text/javascript" src='external.js'></script>
    <img src="/test.gif" BORDER=0 WIDTH=1 HEIGHT=1 >
    
    </body>
    </html>


Contents of external.js: 

    for(i=0; i<999999; i++){ ; }


I notice that when a request to test.gif results in a 404 or 302, Firefox makes another request for that same resource immediately after the script has completed. 

   127.0.0.1 - - [29/Apr/2011:16:22:22 -0400] "GET /test.gif HTTP/1.1" 404 507 
   127.0.0.1 - - [29/Apr/2011:16:22:22 -0400] "GET /test.gif HTTP/1.1" 404 507

This behavior doesn't occur for inline javascript, and I have pipelining turned off, so I'm fairly certain it's not related to that. Seems like odd behavior, or I'm just missing something not-so-obvious. Any ideas?

I'm noticing some unusual behavior in Firefox when I include an image directly after a call to an external script which is long-running. For example: <pre><nowiki> <html> <body> <script type="text/javascript" src='external.js'></script> <img src="/test.gif" BORDER=0 WIDTH=1 HEIGHT=1 > </body> </html> </nowiki></pre> <br /> Contents of external.js: <pre><nowiki> for(i=0; i<999999; i++){ ; } </nowiki></pre> <br /> I notice that when a request to test.gif results in a 404 or 302, Firefox makes another request for that same resource immediately after the script has completed. 127.0.0.1 - - [29/Apr/2011:16:22:22 -0400] "GET /test.gif HTTP/1.1" 404 507 127.0.0.1 - - [29/Apr/2011:16:22:22 -0400] "GET /test.gif HTTP/1.1" 404 507 This behavior doesn't occur for inline javascript, and I have pipelining turned off, so I'm fairly certain it's not related to that. Seems like odd behavior, or I'm just missing something not-so-obvious. Any ideas?

Muokattu , muokkaaja cor-el

Kaikki vastaukset (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

This forum focuses on end-user support. You can find more web development help on the mozillaZine Web Development board. Separate forum, separate registration. Please note the tips in the Sticky Post at the top of the forum before posting.