Anjana Fernando created AXIS2-5477:
--------------------------------------
Summary: Incorrect Behavior in HTTP Request Header Retrieval from
MessageContext
Key: AXIS2-5477
URL: https://issues.apache.org/jira/browse/AXIS2-5477
Project: Axis2
Issue Type: Bug
Components: transports
Affects Versions: 1.6.2
Reporter: Anjana Fernando
When getting HTTP transport header map from the message context, the case
in-sensitiveness is not retained. Basically, the class
org.apache.axis2.transport.http.TransportHeaders has an incorrect behavior,
where it loads all the headers into an internal Map in the init() method and
subsequent calls to get() will be incorrect, specially where in Tomcat, when
asking for the list of header names, it returns everything in lower case, so if
a user ask for a header like "Host", it will not work, because TransportHeaders
class internal map will have an entry called "host", if the init() is not
called, this will work, because it will directly call request.getHeader() ..
which would work for any combination, because that operation is not case
sensitive.
The above init() method of TransportHeaders class is called for operations like
add/size/remove operations, so if any such method method is called, the get()
operations after that will most probably be incorrect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
