This content has been marked as final.
Show 3 replies
-
1. Re: HTTP 400. Bad request! Sit! Stay!
nickarls Dec 1, 2008 6:08 AM (in response to nickarls)It turns out that telnetting to the DNS name port 80 and doing a "GET /" returns the page just fine.
Is it some conspiracy amongst all browsers to consider a response as bad if it comes from a hostname it didn't expect? And if so, what is the remedy? Some alias or virtual host in JBoss?
Thanks in advance,
- Nik -
2. Re: HTTP 400. Bad request! Sit! Stay!
nickarls Dec 1, 2008 7:17 AM (in response to nickarls)More specifically, dumping the reponse headers gives
null: HTTP/1.1 400 No Host matches server name thehost.thedomain.com Transfer-Encoding: chunked Date: Mon, 01 Dec 2008 12:11:43 GMT Connection: close Server: Apache-Coyote/1.1
ping thehost.thedomain.com does lead back to the correct host -
3. Re: HTTP 400. Bad request! Sit! Stay!
nickarls Dec 2, 2008 4:28 AM (in response to nickarls)I tried using virtual hosts and it seems to be working when used from the internal network but the above mentioned error still occurs when coming from an external network.
Network configurations aside, how can this error anyways be related to where the request is originating from?