jakarta-watchdog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Lubke <Ryan.Lu...@Sun.COM>
Subject Re: Host header again.
Date Mon, 04 Feb 2002 13:01:27 GMT
Greg,

Doesn't pay to rush does it :).

Fixed.

Here is some sample trace output:
*******************************************************************
[java] GetContentLengthTest:
     [java]  [watchdog]  REQUEST: GET
/servlet-tests/GetContentLengthTest HTTP/1.0
     [java]  [watchdog]  REQUEST HEADER: Host: localhost:8080
     [java]  [watchdog]  REQUEST HEADER: Content-Type: text/plain
     [java]  [watchdog]  REQUEST HEADER: Content-Length: 20
     [java]  [watchdog]  RESPONSE STATUS-LINE: HTTP/1.1 200 OK
     [java]  [watchdog]  RESPONSE HEADER: Date: Mon, 04 Feb 2002
12:47:09 GMT
     [java]  [watchdog]  RESPONSE HEADER: Server: Apache Tomcat/4.1-dev
(HTTP/1.1 Connector)
     [java]  [watchdog]  RESPONSE HEADER: Connection: close
     [java]  [watchdog]  RESPONSE BODY:
     [java]  [watchdog] GetContentLengthTest test PASSED
     [java]  [watchdog] 
     [java]  [watchdog]  closing socket
     [java]  [watchdog]  Performing exact match of server response and
goldenfile
     [java]  [watchdog]  PASSED GetContentLengthTest
     [java]  [watchdog]         (GET /servlet-tests/GetContentLengthTest
HTTP/1.0)
     [java] 
     [java] BUILD SUCCESSFUL
     [java] 
     [java] Total time: 2 seconds
*************************************************************

So aside from this problem with the Host header, how goes testing?

Regards,

Ryan Lubke


On Sun, 2002-02-03 at 23:04, Greg Wilkins wrote:
> 
> Ryan,
> 
> Thanks for adding the Host header into watchdog - however there is still
> a problem.
> 
> By default you are only setting
> 
>    Host: localhost
> 
> when you should be setting
> 
>    Host: localhost:8080
> 
> 
> The RFC says:
> 
>     Host = "Host" ":" host [ ":" port ] ; Section 3.2.2
> 
>     A "host" without any trailing port information implies the default
>     port for the service requested (e.g., "80" for an HTTP URL).
> 
> So even though Jetty receives the requests on port 8080, getServerPort
> returns 80, as this is what the Host header indicates the client used
> for their request and that some proxy or gateway did the redirection to
> port 8080.
> 
> Note that there is even a difference between
> 
>    Host: localhost:80
> 
> and
> 
>    Host: localhost
> 
> As some browsers treat cookies set for localhost:80 as being for a different host
> than just localhost.    So Jetty tries to be rigorous when rewriting URLs to always use
> the exact form that was specified in the host header.
> 
> 
> cheers
> 
> 
> 
> cheers
> 
> 
> -- 
> Greg Wilkins<gregw@mortbay.com>          GB  Phone: +44-(0)7092063462
> Mort Bay Consulting Australia and UK.    Mbl Phone: +61-(0)4 17786631
> http://www.mortbay.com                   AU  Phone: +61-(0)2 98107029
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:watchdog-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:watchdog-dev-help@jakarta.apache.org>
> 



--
To unsubscribe, e-mail:   <mailto:watchdog-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:watchdog-dev-help@jakarta.apache.org>


Mime
View raw message