[
https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250159#comment-13250159
]
Leif Hedstrom commented on TS-1187:
-----------------------------------
Not sure I follow here, can you show some code example that doesn't work ? I'm
assuming you are setting the appropriate header buffer? Remember there are four
different headers, some of which are not available in all hooks.
I'm going to move this out to 3.3.0, unless you feel it's a bug that needs to
be fixed for 3.2.
> 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
