[
https://issues.apache.org/jira/browse/AXIS2-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985310#action_12985310
]
Isuru Eranga Suriarachchi commented on AXIS2-4754:
--------------------------------------------------
Andreas,
The JAX-WS specification says "A map of the HTTP headers for the request
message. The key is the header name. The value is a list of values for that
header". It doesn't specifically mention how it is sent at the transport level.
And also, according to RFC 2616 [1], "Multiple message-header fields with the
same field-name MAY be present in a message if and only if the entire
field-value for that header field is defined as a comma-separated list [i.e.,
#(values)]". So isn't it possible to use this to support "multiple value"
headers at JAX-WS level?
Thanks,
~Isuru
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
> Cannot pass HTTP headers with multiple values
> ---------------------------------------------
>
> Key: AXIS2-4754
> URL: https://issues.apache.org/jira/browse/AXIS2-4754
> Project: Axis2
> Issue Type: Bug
> Components: jaxws
> Affects Versions: 1.5.1, 1.5
> Reporter: Jarek Gawor
> Assignee: Isuru Eranga Suriarachchi
> Fix For: 1.6
>
>
> JAX-WS enables a user to pass a map of custom http headers with the request
> (by setting MessageContext.HTTP_REQUEST_HEADERS property on the
> BindingProvider). The map is a mapping of a header name to a list of values.
> Right now Axis2 seems to be handling a single value. If multiple values are
> passed an exception is generated in TransportHeadersAdapter.
> In revision 958078 I added a test case (with commented out code) that might
> be helpful in debugging this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
