Bug 115986 - Empty Host header causes tux to return 404 (or forward)
Empty Host header causes tux to return 404 (or forward)
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: tux (Show other bugs)
3.0
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Ingo Molnar
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-17 09:26 EST by Ville Lindfors
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-18 07:34:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ville Lindfors 2004-02-17 09:26:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6)
Gecko/20040206 Firefox/0.8

Description of problem:
Present, but empty Host header causes tux to return 404



Excerpt from RFC2616 section 14.23

A client MUST include a Host header field in all HTTP/1.1 request
messages . If the requested URI does not include an Internet host
name for the service being requested, then the Host header field MUST
be given with an empty value. 

Version-Release number of selected component (if applicable):
tux-3.2.14-1, kernel-2.4.21-4.EL

How reproducible:
Always

Steps to Reproduce:
# telnet localhost 80
Trying 127.0.0.1...
Connected to (127.0.0.1).
Escape character is '^]'.
GET / HTTP/1.1
Host:

HTTP/1.1 404 Not Found
Connection: Keep-Alive
Content-Length: 29

<HTML> Page Not Found </HTML>
HTTP/1.1 404 Not Found
Connection: Keep-Alive
Content-Length: 29

<HTML> Page Not Found </HTML>Connection closed by foreign host.



# telnet localhost 80
Trying 127.0.0.1...
Connected to (127.0.0.1).
Escape character is '^]'.
GET / HTTP/1.0
Host: foo

HTTP/1.1 200 OK
Content-Type: text/html
Date: Tue, 17 Feb 2004 14:10:15 GMT
Server: TUX/2.0 (Linux)
Content-Length: 0
ETag: "0-eadccacg"
Accept-Ranges: bytes
Last-Modified: Tue, 17 Feb 2004 14:07:34 GMT


Actual Results:  404 not found

Expected Results:  200, page served
Comment 1 Ingo Molnar 2004-08-18 07:34:08 EDT
This is one of the 'weird' requests that Tux rather redirects to
Apache than deal with directly.

Note You need to log in before you can comment on or make changes to this bug.