PQ69058: PQ62683 CHANGED THE BEHAVIOR OF THE WAS PLUGINS SO WE USE THE PORT FROM THE HOST HEADER, DEFAULT TO SERVER PORT IF NO PORT GIVEN

APAR status
Closed as duplicate of another APAR.

Error description

PQ62683 changed the behavior of the WebSphere plugin to meet
the HTTP 1.1 Header field Definitins specifications in 14.23
HOST. Specification is as follows:
14.23 Host
The Host request-header field specifies the Internet host
and port number of the resource being requested, as obtained
from the original URI given by the user or referring
resource (generally an HTTP URL, as described in section
3.2.2). The Host field value MUST represent the naming
authority of the origin server or gateway given by the
original URL. This allows the origin server or gateway to
differentiate between internally-ambiguous URLs, such as the
root "/" URL of a server for multiple host names on a single
IP address.
       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). For example, a request on the origin server for
<http://www.w3.org/pub/WWW/> would properly include:
       GET /pub/WWW/ HTTP/1.1
       Host: www.w3.org
A client MUST include a Host header field in all HTTP/1.1
request messages . If the requested URI does not include
an Internet host name for the service being requested,
then the Host header field MUST be given with an empty
value. An HTTP/1.1 proxy MUST ensure that any request
message it forwards does contain an appropriate Host
header field that identifies the service being requested
by the proxy. All Internet-based HTTP/1.1 servers MUST
respond with a 400 (Bad Request) status code to any
HTTP/1.1 request message which lacks a Host header field.
See sections 5.2 and 19.6.1.1 for other requirements
relating to Host.
Local fix Problem summary Problem conclusion Temporary fix Comments
This is a duplicate of APAR 
PQ72069 .
Originally, this APAR was opened to document a change inthe way
the plugins interpret port numbers that wasintroducedin Fix
Pack 4.0.4.  This change fixed areal problem, but had the
potential to break configurations that had been working before,
so it needed to be documented.  Since this APAR was opened, the
plugin has been changed so the port number interpretation can be
controlled in the plugin configuration (
PQ72069).  Since this
configuration option is implemented and documented, the need for
a separate piece of documentation on this issue has disappeared.
APAR information
APAR number PQ69058
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED DUA
PE NoPE
HIPER NoHIPER
Submitted date 2002-12-11
Closed date 2003-08-12
Last modified date 2003-08-12

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2202

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69058
IBM Group: Software Group
Modified date: Aug 12, 2003