I saw that some changes were made to tcpmon but noticed that this is still a problem. Has anyone had a chance to look at it? To reiterate, the issue is that tcpmon is not using the target hostname in the host header field. For example, if tcpmon is listening for requests on port 8888 and forwarding them to www.myserver.com, the Host header field on the request will say "localhost:8888" rather than "www.myserver.com". For servers that use the Host header field to do something, this is a problem, for example, if you are dynamically generating the wsdl from a .NET web service all the addresses in the wsdl will be wrong.
-Alex >>-----Original Message----- >>From: Alex Glosband >>Sent: Thursday, February 28, 2002 11:55 AM >>To: '[EMAIL PROTECTED]' >>Subject: Tcpmon problem >> >> >>Tcpmon is not setting the Host header field on the http >>request message correctly. It is using the hostname and port >>number that was used to call tcpmon and not the target host >>and port number. This is giving us problems when using tcpmon >>to test interoperability with .NET services, because .NET >>uses the hostname from the Host header field to specify >>addresses in the wsdl it generates. >> >>Also noticed when I changed the header and resent the request >>that the response message tcpmon displayed was truncated. Is >>there some reason it does not display all of the response >>when the request is resent? >> >> >> >>------------------------- >>Alex Glosband >>JRun QA Engineer >>Macromedia >>617.219.2399 >>[EMAIL PROTECTED] >> >>
