Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1568899216.1121960589479.JavaMail.jira@ajax.apache.org>
Date: Thu, 21 Jul 2005 17:43:09 +0200 (CEST)
From: "Srinath Perera (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-76) Need for HTTP HEADER information
In-Reply-To: <30072696.1121405529773.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ 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