85499 - HEAD http://mozilla.org returns "404 Not Found"

Status: VERIFIED DUPLICATE of bug 107166

(mozilla.org Graveyard :: Server Operations, task)

Description

[Henrik Gemal]

Something is configured wrong on mozilla.org.
If you from a unix command line performs the following command:
HEAD mozilla.org

you get:
404 Not found
Connection: close
Date: Tue, 12 Jun 2001 20:46:15 GMT
Server: Netscape-Enterprise/3.6
Content-Length: 207
Content-Type: text/html
Client-Date: Tue, 12 Jun 2001 20:45:12 GMT
Client-Peer: 207.200.81.215:80

If you do the same on netscape.com

HEAD netscape.com
200 OK
Connection: close
Date: Tue, 12 Jun 2001 20:46:22 GMT
Server: Netscape-Enterprise/4.1
Content-Length: 0
Content-Type: text/html
Client-Date: Tue, 12 Jun 2001 20:46:20 GMT
Client-Peer: 207.200.89.225:80
Set-Cookie: 
UIDC=194.192.187.68:0992378783:399753;domain=.netscape.com;path=/;expires=31-
Dec-2010 23:59:59 GM

there nothing wrong with browsing the site, it just the web server that's 
returning a wrong HTTP status code.

Btw: the same is true for www.mozilla.org

HEAD http://bugzilla.mozilla.org
works just fine, returning "200 OK"

Comment 1

[Stephen Brown]

This is a side effect of having "Directory Indexing" turned to off within
the Netscape Enterprise Server 3.6.  If you do a "HEAD" of a specific 
file, i.e. "HEAD mozilla.org/index.html" you will get a successful return
code and actual data returned.  We usually prefer to leave the directory
indexing feature turned off so people can't just generically troll through
the web site and find all the content.  I think in NES 4.1 you get a correct
return code in this instance, though.  I'll verify that and then see about
upgrading install base for www.mozilla.org.

Comment 2

[Risto Kotalampi]

Please note that indexing is turned off on purpose and before touching it 
please make sure security os covered:

http://bugzilla.mozilla.org/show_bug.cgi?id=41158

Comment 3

[Risto Kotalampi]

*** This bug has been marked as a duplicate of 107166 ***

Comment 4

[Martin Sch]

This one is not resolved, the error still exists!

Comment 5

[Henrik Gemal]

verified dupe

Comment 6

[Joe McCabe]

NES6 correctly returns a 200 in reply to

HEAD / HTTP/1.0