Closed
Bug 292767
Opened 20 years ago
Closed 20 years ago
Page cannot be displayed: an apache info page appears instead.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: h.wansing, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0 Calling the url above, doesn't show the content of the page. Instead of that the apache web server shows this info page about what went wrong: http://httpd.apache.org/docs-2.0/howto/public_html.html Mozilla 1.7.5 shows the content correctly. Reproducible: Always Steps to Reproduce: 1. call http://cvs.infodrom.org/public_html/src/Writing/DWN/?cvsroot=infodrom.org#dirlist
Comment 1•20 years ago
|
||
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050503 Firefox/1.0+ WFM Could this have been a transient glitch on the server?
Comment 2•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050419 Firefox/1.0.4 WFM, I'm learning about per user web directories. Sidenote: Upgrade from Firefox 1.0 to 1.0.3 please. http://www.mozilla.org/products/firefox/all.html
Comment 3•20 years ago
|
||
Ah, misread the bug, thought the apache page wasn't showing up. The CVS page loads properly too, listing files as it should.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•20 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
Comment 4•20 years ago
|
||
I got this in email, reportedly received at 7:35 am: I upgraded to 1.0.3 - now my bookmarks are gone! Fine :-(( And I still can't display http://cvs.infodrom.org/public_html/src/Writing/DWN/?cvsroot=infodrom.org#dirlist Then I renamed my <home>/.firefox and .mozilla dir, let them get newly created, and now it works. Holger
You need to log in
before you can comment on or make changes to this bug.
Description
•