Closed
Bug 243495
Opened 20 years ago
Closed 19 years ago
HTTP Status 408
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 248827
People
(Reporter: mauro, Assigned: darin.moz)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.6) Gecko/20040207 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; it-IT; rv:1.6) Gecko/20040207 Firefox/0.8
With Tomcat 5.0.24 Firefox don't works.
With Mozilla, Konqueror, IE.
With Tomcat 5.0.19 also Firefox Works
Reproducible: Always
Steps to Reproduce:
1. Enter page-login OK, click login
2. Open a login-page con j_security_check
3. Error 408
Actual Results:
HTTP Status 408 - The time allowed for the login process has been exceeded. If
you wish to continue you must either click back twice and re-click the link you
requested or close and re-open your browser
type Status report
message The time allowed for the login process has been exceeded. If you wish to
continue you must either click back twice and re-click the link you requested or
close and re-open your browser
description The client did not produce a request within the time that the server
was prepared to wait (The time allowed for the login process has been exceeded.
If you wish to continue you must either click back twice and re-click the link
you requested or close and re-open your browser).
Apache Tomcat/5.0.24
Updated•20 years ago
|
Assignee: general → darin
Component: Browser-General → Networking: HTTP
QA Contact: general → core.networking.http
"The time allowed for the login process has been exceeded. If you wish to
continue you must either click back twice and re-click the link you requested or
close and re-open your browser"
(Let's keep the summarys to 59 characters or less.
Summary: HTTP Status 408 - The time allowed for the login process has been exceeded. If you wish to continue you must either click back twice and re-click the link you requested or close and re-open your browser → HTTP Status 408
Reporter | ||
Comment 2•20 years ago
|
||
This error appear only with Tomcat 5.0.24. Upgrading to Tomcat 5.0.28.
Close this bug
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
REOPEN to INVALID, not necko's fault.
Status: RESOLVED → UNCONFIRMED
QA Contact: networking.http → benc
Resolution: WONTFIX → ---
Assignee | ||
Comment 4•19 years ago
|
||
*** This bug has been marked as a duplicate of 248827 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 19 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•