Overwrite HTTP Header in order to improve interoperability
----------------------------------------------------------
Key: AXIS2-4503
URL: https://issues.apache.org/jira/browse/AXIS2-4503
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: transports
Affects Versions: 1.3, 1.4, 1.4.1, 1.5
Environment: N.A.
Reporter: Thomas Michelbach
Issue number AXIS2-4219 was closed because the desired functionality was not
being interpreted correctly.
But in my view there are cases where HTTP header overwriting is desired because
of interoperability issues.
Some servers do not support chunking and only implement HTTP 1.0. Therefore
there are some limitations how to handle incoming data, specially when this
data is quite large.
In that case it is desired to change the content type of the HTTP header, in
order to inform the application server to handle this special content
differently.
The content type would be set to application/octet-stream, in order to inform
an application server to passthrough the stream of data and do not start
parsing the XML content.
I am trying to use following API:
_serviceClient.getOptions().setProperty(org.apache.axis2.transport.http.HTTPConstants.HEADER_CONTENT_TYPE,"application/octet-stream");
Remark: Currently the HTTP header cannot be overwritten, but new can be added.
In other words, it is possible to set two content types in the same header.
The SOAP specification DOES enforce the text/xml content type:
http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
"HTTP applications MUST use the media type "text/xml" according to RFC 2376 [3]
when including SOAP entity bodies in HTTP messages."
But the cited RFC 2376 DOES also do an explicit exception:
http://www.normos.org/ietf/rfc/rfc2376.html,
In the RFC it is defined like: "Every XML entity is suitable for use with the
application/xml media type without modification. But this does not exploit the
fact that XML can be treated as plain text in many cases. MIME user agents (and
web user agents) that do not have explicit support for application/xml will
treat it as application/octet-stream, for example, by offering to save it to a
file."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
