Those headers are not related to your 400 issue. Deleting them can cause
Frontpage clients to stop working against the server.
As Jeff suggested, the 400 error is happening because your website is
currently configured to require a Host header, but your web browsers were
not told to send a Host header when they did their DNS lookup.
You will have to make the decision here -- either your website should not
require a Host header, or your network configuration is incorrect such that
the browsers are not sending the Host header.
My guess is that since this configuration works for most people, the problem
is likely not with your server configuration. Since a server cannot make
the browser do the right thing (like send a Host header), I think that
people who get 400 errors just have to accept it -- if they don't fix their
networking, you can't do it for them.
--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Dave Munday" <thehappymundays.DeleteThis@hotmail.com> wrote in message
news:%23lPxauIqEHA.708@tk2msftngp13.phx.gbl...
Jeff, this rather like watching paint dry but thanks for hanging in here
I have a defualt website which has the following entries under Custom HTTP
headers
MicrosoftOfficeWebServer: 5.0_Pub
X_powered-By: ASP.NET
are these entries okay to delete
Dave
"Jeff Cochran" <jeff.nospam.DeleteThis@zina.com> wrote in message
news:415b434c.480985530@msnews.microsoft.com...
> On Wed, 29 Sep 2004 20:14:14 +0200, "Dave Munday"
> <thehappymundays.DeleteThis@hotmail.com> wrote:
>
> >many thanks for your reply, you must excuse my ignorance but I inherited
an
> >IIS 4.0 site that was running on NT4.0 when it came to migrate to Windows
> >2003 I used the migration tool to take it forward
> >
> >How can I tell if I am using host headers
>
> First would be if you have more than one site. Second to check is
> that all the sites use the same IP, in the properties for each site
> look at the IP. Third is to check the host header, check each site's
> properties under the Web Site tab, advanced button.
>
> Jeff
>
> >"Jeff Cochran" <jeff.nospam.DeleteThis@zina.com> wrote in message
> >news:415c102b.402366352@msnews.microsoft.com...
> >> On Tue, 28 Sep 2004 20:23:37 +0200, "Dave Munday"
> >> <thehappymundays.DeleteThis@hotmail.com> wrote:
> >>
> >> >A while back I posted with regard to the above error message;
> >> >
> >> >following the advice I have turned off show friendly errors
> >> >
> >> >the displayed message is now
> >> >
> >> >Host Header Required
> >> >
> >> >Description: Your Broswer did not send a "Host" HTTP header field and
> >> >therefore the virtual host being requested could not be determined. To
> >> >access this website correctly, you will need to upgrade to a broswer
that
> >> >supports HTTP "Host" header field
> >> >
> >> >my clients are running IE6.0
> >> >
> >> >Thanks for any help
> >>
> >> Huh? I haven't seen this error in years. Nothing current should
> >> generate it. Are you using host headers in IIS?
> >>
> >> Jeff
> >
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: HTTP 400 - Bad Request