1

The network.http.response.timeout was changed from not being set in Firefox version 28 to a default limit of 300 (5 minutes) in version 29. (see this blog entry at morgb.blogspot.de).

I would like to change it back to a higher value, if needed with the help of a Firefox-Addon.

Or add a warning to my web-application (which needs the longer timeout for several reasons).

rubo77
  • 19,527
  • 31
  • 134
  • 226
  • Or do I have to reprogram my web-app so only `XMLHttpRequests` use such long loading-times? – rubo77 May 21 '14 at 12:43
  • Also, you can check the answer at: [https://stackoverflow.com/a/47754398/1841710](https://stackoverflow.com/a/47754398/1841710) – Eli Dec 03 '19 at 10:33

1 Answers1

1

Create an addon called "response-timeout-24-hours" with the addon-sdk and put this in your main.js 

const {Cc,Ci} = require("chrome");
var pref = Cc["@mozilla.org/preferences-service;1"].getService(Ci.nsIPrefBranch);
console.log(pref.setIntPref("network.http.response.timeout", 3600*24));
console.log("timeout set to "+pref.getIntPref("network.http.response.timeout")+"s by response-timeout-24-hours");
rubo77
  • 19,527
  • 31
  • 134
  • 226
rb-webdev
  • 26
  • 1
  • 1
    I created this addon here: https://addons.mozilla.org/en-US/firefox/addon/response-timeout-24-hours/ – rubo77 May 21 '14 at 20:45
  • Still todo: [How do I check if the addon is installed with javascript?](http://stackoverflow.com/a/23812866) – rubo77 May 22 '14 at 16:52
  • I have a problem now: the add-on wasn't accepted with the following reason: *"Add-ons which change critical settings must revert the changes when disabled or uninstalled. You should also make the changes in the default, rather than the user, branch."* – rubo77 Jun 01 '14 at 22:37