Bug 84974 - Installer does not properly implement HTTP/1.1
Installer does not properly implement HTTP/1.1
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-02-24 11:08 EST by Mike Cumings
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-24 12:17:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Cumings 2003-02-24 11:08:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920

Description of problem:
During HTTP-based installation I discovered that the installer
is sending HTTP queries in the following format:

GET /RedHat/some/path HTTP/1.1

According the the HTTP spec the above should be implemented as:

GET /RedHat/some/path HTTP/1.1
Host: installserver.company.com

This causes some confusion with virtual hosting and proxy caching.
Either revert back to HTTP/1.0 or properly implement the 1.1 spec.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Start a HTTP-based install
2. Snoop the net traffic
3. Observe the nonconformance

Actual Results:  Install fails.

Expected Results:  Install succeeds.

Additional info:

The HTTP installs do NOT work properly when using a Solaris-based
server running Apache or Squid.  It does seem to work however, when
a lighter weight HTTP daemon such as thttpd is used.  Tunneling
thttpd through Squid fails.  Failure mode is an incomplete filesystem
image being mounted and then a lot of "attempted read past end
of device" type messages.
Comment 1 Jeremy Katz 2003-02-24 12:17:30 EST
This is fixed in newer releases.

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