309815 - Content negotiation: problems with linking to contact page

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[nexuslite]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 (ax)

Firefox 1.0.7 with content negotiation does not go from / to /contact or from
/contact to /  where / initiates file index.php and /contact initiates file
/contact.php (directory must be root and web address with no prefix i.g.
www.site.com or bugs.site.com. site must be site.com) on http://nexuslite.org/ I
put a menu link on the side for bug reproduction. also
http://nexuslite.org/contact the main home link is the other link to try from
the contacts page. However nexuslite.org goes up and down frequently as its my
development site.

Reproducible: Always

Steps to Reproduce:
1. turn on content negotiation on the server (using apache 2.0.45 Win32)
2. in the root directory create contact.php and index.php put the folowing line
in each ->  <a href="/">Home</a><a href="/contact">Contact</a>
3. go to the site in firefox and try and click on the links

Actual Results:  
Nothing! Firefox just keeps trying to load the page but never does

Expected Results:  
Load the page

Comment 1

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 2

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.