Closed
Bug 214346
Opened 21 years ago
Closed 21 years ago
strange name resolving behaviour
Categories
(SeaMonkey :: Location Bar, defect)
Tracking
(Not tracked)
CLOSED
INVALID
People
(Reporter: Stappers, Assigned: hewitt)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2 Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2 When trying to visit http://www.alioth.debian.org/projects/skami I see "Resolving host alioth.debian.org..." After some time the alert box "alioth.debian.org" could not be found. Please check the name and try again." Where is the "www." gone? On the same computer I can do this: $ host www.alioth.debian.org www.alioth.debian.org A 192.87.30.200 $ host alioth.debian.org Nameserver not responding alioth.debian.org A record not found, try again $ Reproducible: Always Steps to Reproduce: See "Details" Actual Results: The alert box Expected Results: Display the contens of the site.
Comment 1•21 years ago
|
||
I don't think this is a mozilla issue. The site seems to be working now, and note that the URL still changes to http://alioth.debian.org/projects/skami, stripping the www. This is, I think, a function of the webserver (at Debian) presenting what it considers to be the canonical form of its URL. Nothing whatsoever to do with mozilla. Or am I missing something?
Comment 2•21 years ago
|
||
% wget -s -O ~/foo.html 'http://www.alioth.debian.org/projects/skami' --18:32:46-- http://www.alioth.debian.org/projects/skami => `/home/bzbarsky/foo.html' Resolving www.alioth.debian.org... done. Connecting to www.alioth.debian.org[192.87.30.200]:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://alioth.debian.org/projects/skami [following] So the host just sends a redirect, and the hostname it redirects to was not resolving.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•21 years ago
|
||
So it looks like that the name resolving problem is outside Mozilla. --- Did checking of name servers. --- On the name server computer '/etc/init.d/bind stop', '/etc/init.d/bind start' and the problem was gone. --- Thank you. I will close the bug.
Status: RESOLVED → CLOSED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•