Dealing with Web Services that use HTTP 1.0 protocol
 Technote (troubleshooting)
 
Problem(Abstract)
HTTP 404 return code on request from Java / Web Service HTTP 1.0 client
 
Cause
Java / Web Service clients are not required to send a port value on the host header for HTTP 1.0. When a Web Services client makes a request implementing HTTP 1.0 protocol, it is not required to send a port in the host header. When a request arrives at WebSphere Application Server in this fashion, WebSphere must make a determination as to what the port is.. unless there is a via header, WebSphere will assume port 80 by default. This may cause a 404 to be thrown if WebSphere is not listening (or configured to handle) port 80. For the most part, web browsers use HTTP 1.1 protocol, so this would not be an issue.
 
Resolving the problem
An easy circumvention is to add a virtual host definition to WebSphere with port 80, in addition to the existing virtual host definitions.
 
 
 


Document Information


Current web document: swg21112258.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Web Services(for example: SOAP or UDDI or WSGW/WSIF)
Operating system(s): z/OS
Software version: 5.0
Software edition:
Reference #: 1112258
IBM Group: Software Group
Modified date: Jun 11, 2003