273606 - http://ip.ngilmore.com/ doesn't load virtual host. http://ip.ngilmore.com/anything loads correctly.

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Norman Gilmore]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041207
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a6) Gecko/20041207

The following URLs all correctly load the same Apache virtual host page.
http://ngilmore.com/
http://www.ngilmore.com/
http://ip.ngilmore.com/index.html
http://cname.ngilmore.com/index.html

From this, we can see that DNS and Virtual host parameters are configured correctly.

These two URLs do not work correctly. They load the Server root (no virtual host)
http://ip.ngilmore.com/
http://cname.ngilmore.com/

I have placed a test page at http://ngilmore.com/ so you can reproduce it in 6
clicks.


Reproducible: Always
Steps to Reproduce:
Enter URLs in "Details" box above.
Actual Results:  
The first 4 URLs correctly loaded the Apache virtual host.
The last two URLs did not load the virtual host, but the default root.


Expected Results:  
All URLs should load the virutal host.


I searched on terms CNAME and DNS looking for dupes, and reviewed frequently
posted bugs, so I hope this is a new one. But it seems so easy to stumble
across, I'm sure it must have been reported by now.

Comment 1

[Norman Gilmore]

I just got a suggestion from someone to force a refresh.

Gee, it refreshes and loads the correct page from then on.

However, the fact remains that it did not load the page correctly even after a
reboot of the machine, and the Ctrl-F5 was REQUIRED in order to unglitch it.

I installed the nightly build in addition to my normal Mozilla 1.7.3. Oddly,
1.7.3 also started functioning right away without a Ctrl-F5. I guess both copies
are using the same cache?

Comment 2

[Boris Zbarsky [:bzbarsky]]

It sounds like you just had a cache entry from before the vhost was set up in
your browser cache....

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.