Closed Bug 72918 Opened 24 years ago Closed 20 years ago

HTTP Sessions time out too early

Categories

(Core :: Networking: HTTP, defect, P4)

x86
Windows NT
defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: c121hains, Unassigned)

Details

(Keywords: verifyme)

/components/nsXmlRpcClient.js contains the line: throw Components.Exception('Connection timed out'); for a while loop that checks if(!input.available()) //wait for data -------- Is this directly related to the timeout issue? Netscape times out too early for my web sever to respond. My webserver wont respond for 3 minutes. Netscape always times out after approx 2 min 13 sec. I must fix this.
networking, over to gagan.
Assignee: mcafee → gagan
Component: Preferences → Networking
re: bug 36838 Your comment: ------- Additional Comments From ruslan 2000-04-24 18:35 ------- Is it timing out right away or after a while? I just adjusted response timeout up to 120 seconds by default (it was 30 seconds). This is a hard coded value? Netscape 6/6.01 times out after 2 min before my server can respond to it. My server takes up to 3 min to respond. Is there any way to change this value? Any way to change this value with javascript? (wishful thinking).
over to ruslan
QA Contact: sairuh → tever
neeti
Assignee: gagan → neeti
Keywords: qawanted
Where is Netscape 6/6.01 'prefs.js' file??? For earlier versions it was: \ProgramFiles\Netscape\Users\<user name>\prefs.js Modifying 'all.js' and even deleting it makes no changes.
prefs.js is in you profile directory. Search for users50 directory under winnt. c:\winnt\profiles\<user>\Application Data\Mozilla\Users50 Neeti
Is this still a problem?
This sounds like an HTTP conformance issue. I was unable to locate the timeout specification for a User Agent in the HTTP RFC's, but I *was* able to verify the timeout values specified by the reporter. Since this is what the Reporter is alleging, marking NEW. If this is correct behavior (i.e. mozilla is conforming to spec on how long a timeout should be), feel free to mark WONTFIX. :)
Severity: critical → major
Status: UNCONFIRMED → NEW
Component: Networking → Networking: HTTP
Ever confirmed: true
Keywords: correctness
Summary: Netscape 6 times out too early → Mozilla HTTP Sessions time out too early
cc'ing darin
Target Milestone: --- → mozilla0.9.2
Priority: -- → P4
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.5
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Target Milestone: mozilla0.9.6 → mozilla0.9.8
Reporter: Is this still a problem?
Target Milestone: mozilla0.9.8 → mozilla1.0
Target Milestone: mozilla1.0 → Future
moving neeti's futured bugs for triaging.
Assignee: neeti → new-network-bugs
The comments below seem to refer to Netscape 6. But in Mozilla 2003010908, I get a 'Timed out' message after about a minute, which prevents slow sites from being accessed. (This does not happen in Netscape 4.79.) There is nothing about this in Mozilla Help.
hmm.. i think the only timeout mozilla explicitly imposes is a 35 second connection attempt timeout. if we don't get a connection after 35 seconds, then you will see that error. is that how long you are waiting? it is possible that the operating system or some lower layer is generating a timeout error as well.
Darin, no, when I tried it yesterday it took 67 seconds. And since Netscape 4.79 did not impose any 'timed out' limit on the same web-site, I assume that it was Mozilla and not my system or my ISP that imposed the 67" one when I used Mozilla.
Michael, this bug originally is concerned with HTTP session timeout, which is a timeout from an established TCP/IP connection. It sounds like you and Darin are talking about a timeout during the initial connection establishment, which comes from a failure of the three-way handshake. The timeout would vary by OS (and the apparent latency would also depend on your DNS performance).
Keywords: qawanted
'Benc', I think you must be right. I tried it again and it took 71 seconds this time. Also no 'Time out' happens when other slow-loading sites are loading and the progress bar at the bottom of the screen shows activity.
Just to wrap up: over the years I think I have seen two or three bugs that mentioned the HTTP-level application timeout was either 120 or infinity. I have not been the lead HTTP tester, so I never nailed this down.
I don't understand all this stuff on this page but I am having a major problem with my sites being timed out a lot. Can't get to some of the sites. Please help me. I have XP. Thank You: Cherry
Cherry, please file a new bug. Put a full description of the problem (what you type, what happens, what you see, etc.) Most of this bug discusses behavior that was removed a long time ago.
Status: NEW → RESOLVED
Closed: 20 years ago
Keywords: verifyme
QA Contact: tever → benc
Resolution: --- → WORKSFORME
Summary: Mozilla HTTP Sessions time out too early → HTTP Sessions time out too early
You need to log in before you can comment on or make changes to this bug.