24Dec2007 (UTC +8) On 12/24/07, John Peter Loh <[EMAIL PROTECTED]> wrote: > They (third party) connect directly to us and they've been using > HTTP/1.1 even when everything was fine. I am almost definite that their > app stopped sending the host header that caused the 400 errors. > > We're using name-based virtual hosting and everything was working fine. > We didn't change anything in our configuration. > > I also simulated the requests with and without the Host field with > telnet on various web servers that were working fine. > > This turned to a case of admitting who's the one doing the wrong thing.
Run wireshark and/or Paros Proxy, and see what's happening on "the wire". That will give you definite answers on what happens before and after the 400 errors with your Apache. Drexx Laggui -- CISA, CISSP, CFE Associate, CCSI, CSA http://www.laggui.com ( Singapore / Manila / California ) Computer forensics; Penetration testing; QMS & ISMS developers; K-Transfer PGP fingerprint = 6E62 A089 E3EA 1B93 BFB4 8363 FFEC 3976 FF31 8A4E _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
