Closed
Bug 726248
Opened 14 years ago
Closed 14 years ago
504 Gateway Time-out 503 Service Unavailable
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: waleed123435, Unassigned)
Details
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.2; SIMBAR={E7C48371-2B4C-11E1-A17A-001FD01C2F1D}; InfoPath.2; AskTbVDJ/5.11.3.15590; BRI/2)
Steps to reproduce:
504 Gateway Time-out
The server didn't respond in time
503 Service Unavailable
No server is available to handle this request
Actual results:
504 Gateway Time-out
The server didn't respond in time
503 Service Unavailable
No server is available to handle this request
Expected results:
504 Gateway Time-out
The server didn't respond in time
503 Service Unavailable
No server is available to handle this request
Comment 1•14 years ago
|
||
Both 504 Gateway Time-out and 503 Service Unavailable are error codes generated by the server, indicating problems with the server itself and the connected infrastructure, and have generally nothing to do with the web browser.
If you in spite of that have found that it's indeed a problem with Firefox, then first read the links below and feel free to reopen the bug.
https://quality.mozilla.org/docs/bugzilla/starter-kit/how-to-write-a-proper-bug/
https://developer.mozilla.org/en/Bug_writing_guidelines
And if your intention was just to test Bugzilla - don't do that. This is a live Bugzilla instance and potentially a lot of people get activated to no avail.
Use http://landfill.bugzilla.org/ if you want to test things.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•