You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Vicky Kumar (JIRA)" <ji...@apache.org> on 2005/07/15 07:32:09 UTC
[jira] Created: (AXIS2-76) Need for HTTP HEADER information
Need for HTTP HEADER information
--------------------------------
Key: AXIS2-76
URL: http://issues.apache.org/jira/browse/AXIS2-76
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: transports
Versions: 0.9
Reporter: Vicky Kumar
Currently AXIS2 engine parses the content of the HTTP request Header but discards the content without adding them to the message context. This impairs users from accessing various details which can be sent in the HTTP Header by a client/consumer(The Authorization detail for example).. The availability of functionality to access the HTTP Header info would help in various scenarios.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS2-76) Need for HTTP HEADER information
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-76?page=all ]
Srinath Perera resolved AXIS2-76:
---------------------------------
Resolution: Fixed
set to MessageContext agiest the property MessageContext .TRANSPORT_HEADERS
> Need for HTTP HEADER information
> --------------------------------
>
> Key: AXIS2-76
> URL: http://issues.apache.org/jira/browse/AXIS2-76
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: transports
> Versions: 0.9
> Reporter: Vicky Kumar
> Assignee: Srinath Perera
>
> Currently AXIS2 engine parses the content of the HTTP request Header but discards the content without adding them to the message context. This impairs users from accessing various details which can be sent in the HTTP Header by a client/consumer(The Authorization detail for example).. The availability of functionality to access the HTTP Header info would help in various scenarios.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXIS2-76) Need for HTTP HEADER information
Posted by "Srinath Perera (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-76?page=all ]
Srinath Perera reassigned AXIS2-76:
-----------------------------------
Assign To: Srinath Perera
> Need for HTTP HEADER information
> --------------------------------
>
> Key: AXIS2-76
> URL: http://issues.apache.org/jira/browse/AXIS2-76
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: transports
> Versions: 0.9
> Reporter: Vicky Kumar
> Assignee: Srinath Perera
>
> Currently AXIS2 engine parses the content of the HTTP request Header but discards the content without adding them to the message context. This impairs users from accessing various details which can be sent in the HTTP Header by a client/consumer(The Authorization detail for example).. The availability of functionality to access the HTTP Header info would help in various scenarios.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira