Bug 10051 - setting apacher ServerName fails
Summary: setting apacher ServerName fails
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: linuxconf   
(Show other bugs)
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-03-08 10:24 UTC by Florian La Roche
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-04 07:07:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Florian La Roche 2000-03-08 10:24:46 UTC
setting the apache ServerName is reported to not work

Comment 1 odaf 2000-04-04 07:07:59 UTC
I got an strange error related to this. Using IP number to get into web server
goes ok, using a DNS name is runs Ok too, but using the real name of the machine
Bad Request

Your browser sent a request that this server could not understand.

Client sent malformed Host header

Apache/1.3.12 Server at trsc14_40.xunta.es Port 80

Comment 2 Nalin Dahyabhai 2000-09-12 18:49:19 UTC
I suspect DNS resolution problems in both cases.  Clients typically append a
Host: header to their requests, specifying as a virtual host the name you used
for connecting to the server.  If the server does not recognize the name as
equivalent to one of its configured hosts (or the default), it should return an

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