[
https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246627#comment-13246627
]
Eric Ahn commented on TS-1187:
------------------------------
I just figure it out,
It set headers using TSMimeHdrFieldNameSet, looks like "myheader :
header-value".
but can't sent client or origin server.
In case of sending cache to origin server, it appears only header name, that is
"myheader : ", in origin server, but, can't see value "header-value".
> TSMimeHdrFieldNameSet does not work for headers read from the client or
> origin server (but does work for headers added by traffic server)
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TS-1187
> URL: https://issues.apache.org/jira/browse/TS-1187
> Project: Traffic Server
> Issue Type: Bug
> Components: MIME
> Affects Versions: 3.0.2
> Environment: Redhat linux with plugin that wants to rename a header
> read from the client.
> Reporter: Alistair Stevenson
> Labels: api-change
> Fix For: 3.1.4
>
>
> TSMimeHdrFieldNameSet does not work for headers read from the client or
> origin server (but does work for headers added by traffic server)
> The name appears set (and the function returns SUCCESS) but when the data is
> sent to the origin Server it is corrupted at the point where the header is
> set. i.e the header name is sent but the header is corrupted after this.
> I am having to create a new header and copy the values and then destroy the
> original header which is not as efficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
