Re: Debian installation problems, ERROR 400 BAD REQUEST

[Joe C. <jo...@sw...>]

IE has many issues, regardless of configuration.  ;-)

But in this case it is worth mentioning that IE, because it is much 
smarter than you or I, will return "simplified" error messages instead 
of the error message generated by the server by default.  This must be 
manually disabled, if you enjoy seeing useful error messages from time 
to time.  But be careful, though, the error messages you receive from 
the webserver might confuse you or put out your eye.  Thank goodness 
Microsoft are looking out for us.

(To disable this misfeature of IE as well as upgrading the standards 
compliance of your browsing experience, you may wish to go to 
http://www.mozilla.org and download the fix. ;-)

Bill James wrote:
> Very cool that you found the problem
> 
> Although on my XP Pro box with IE 6 it tells me to go to https with SSL
> active if I try just http (just tried it to confirm)
> 
> I wonder if your IE has other config issues
> 
> 
> ----- Original Message -----
> From: "Larry Wall" <lar...@ho...>
> To: <jca...@we...>; <web...@li...>
> Sent: Tuesday, January 14, 2003 6:29 PM
> Subject: Re: Debian installation problems, ERROR 400 BAD REQUEST
> 
> 
> 
>>Hi guys, thanks for the replies. I've found my problem!!
>>
>>1) First of all, you're right Jamie, I didn't clue in that webmin was its
>>own mini webserver... duh! So leaving files in /usr/share/webmin works
> 
> just
> 
>>fine as it turns out.
>>2) Internet Explorer was reporting Error 400 - Bad Request (not 404, as I
>>had erroneously reported).
>>3) After banging my head against the wall trying to figure out why I kept
>>seeing this message, I decided to launch tcpdump protocol analyzer to see
>>what was going on. I was trying to access my Debian box from a windows XP
>>machine running IE6 off the same hub and on the same subnet.
>>tcpdump showed that SYN,ACK http type packets were being sent back and
> 
> forth
> 
>>properly, so I thought this was some sort of webmin/IE incompatibility
>>problem, thus I decided to download Mozilla browser for WinXP to see if
>>somehow a more RFC complient browser would actually work (of course I was
>>already unfairly cursing Billy G. by this time). Well it turns out it
> 
> still
> 
>>didn't work, the SAME problem, ***HOWEVER***, Mozilla was smart enough to
>>suggest to me that the server I was trying to access with:
>>http://a.b.c.d:10000/  was running in SSL mode and thus Mozilla suggested
> 
> I
> 
>>try to access it with "https" instead of "http", and TA-DA, it worked!
> 
> After
> 
>>that I tried in in IE6 and it also worked.
>>
>>Thanks everyone for your prompt replies and hints. Hope this post helps
>>others in the future.
>>Larry

-- 
Joe Cooper <jo...@sw...>
Web caching appliances and support.
http://www.swelltech.com