Buscar en Ayuda

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

At various sites firefox (but not IE) returns Http status code 416: "requested range not satisfiable"; what's the solution?

  • 5 respuestas
  • 8 tienen este problema
  • 11 visitas
  • Última respuesta de graham08

more options

Yes, we are running firefox 5.0 and most likely all the stuff you detected (I don't know how to tell, but they sound like stuff we have)

  • 1.9.0009.1
  • ActiveTouch General Plugin Container Version 105
  • Adobe PDF Plug-In For Firefox and Netscape 10.0.1
  • NPRuntime Script Plug-in Library for Java(TM) Deploy
  • 12.0.1.647
  • RealPlayer(tm) LiveConnect-Enabled Plug-In
  • RealJukebox Netscape Plugin
  • Shockwave Flash 10.2 r152
  • Picasa plugin
  • Next Generation Java Plug-in 1.6.0_25 for Mozilla browsers
  • 4.0.50524.0
  • RealPlayer(tm) HTML5VideoShim Plug-In
  • RealNetworks(tm) RealPlayer Chrome Background Extension Plug-In

Solución elegida

Troubleshooting extensions and themes

Check and tell if its working.

Leer esta respuesta en su contexto 👍 0

Todas las respuestas (5)

more options
more options

I cleared the network history cache first: did not fix completely, but seemed to make it better. Next I cleard the everything out of the cooke cache except the cookies themselves: seemed to make problem much worse! Finally I cleared the cookies themselves: made problem much better, but still not 100%

I think you are onto somethng, mha007. Perhaps the problem occurs as firefox checks to see if the page is already in its cache, or if the page's cookie is on record. Somewhere along the line the request address get screw up.

more options

I cleared the network history cache first: did not fix completely, but seemed to make it better. Next I cleared the everything out of the cooke cache except the cookies themselves: seemed to make problem much worse! Finally I cleared the cookies themselves: made problem much better, but still not 100%

I think you are onto somethng, mha007. Perhaps the problem occurs as firefox checks to see if the page is already in its cache, or if the page's cookie is on record. Somewhere along the line the requested address gets screwed up.

Reply

more options

Solución elegida

Troubleshooting extensions and themes

Check and tell if its working.

more options

I started ff up in "safe mode" - better but not perfect. Next I reset the preferences to ff-default - ran it thru a few dozen links that had always shown up problems, and none occurred. Provisionally, it's fixed !!

  (I'll let you know if the problem resurfaces...  )

Thanks mha007.