Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Stop connection timeouts from happening - want the page to wait

  • 2 відповіді
  • 101 має цю проблему
  • 1 перегляд
  • Остання відповідь від AndyOrange

more options

I run multiple tab that monitor various tools. These pages refresh themselves. The pages have to wait for each other to finish before they can start.

In version 28 this was fine. The page would just wait indefinitely and kick in when a previous page finished doing its thing.

Now in version 29 it returns with a "The connection has timed out" message after some minutes.

I have adjusted

network.http.connection-timeout network.http.pipelining.read-timeout

to high values but problem is still occurring. Any thoughts on how I can return the behavior to FF28?

I run multiple tab that monitor various tools. These pages refresh themselves. The pages have to wait for each other to finish before they can start. In version 28 this was fine. The page would just wait indefinitely and kick in when a previous page finished doing its thing. Now in version 29 it returns with a "The connection has timed out" message after some minutes. I have adjusted network.http.connection-timeout network.http.pipelining.read-timeout to high values but problem is still occurring. Any thoughts on how I can return the behavior to FF28?

Обране рішення

Try adjusting the http.response.timeout setting. In version 28 this was not set. In version 29 it is set to 300 (5 minutes). Increasing it to something much larger should help.

See this blog entry:

http://morgb.blogspot.com/2014/05/firefox-29-and-http-response-timeout.html

Читати цю відповідь у контексті 👍 16

Усі відповіді (2)

more options

Вибране рішення

Try adjusting the http.response.timeout setting. In version 28 this was not set. In version 29 it is set to 300 (5 minutes). Increasing it to something much larger should help.

See this blog entry:

http://morgb.blogspot.com/2014/05/firefox-29-and-http-response-timeout.html

more options

I can confirm that this setting works.

Either setting it to 0 or a very large number returns the behavior to previous.

http.response.timeout = 0 or http.response.timeout = 300000

My scripts now do no time out when waiting.

Thanks.