[jira] [Commented] (TS-1187) TSMimeHdrFieldNameSet does not work for headers read from the client or origin server (but does work for headers added by traffic server)

["Bryan Call (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010222#comment-14010222 ] 

Bryan Call commented on TS-1187:
--------------------------------

[~bwahn]

Can you post a code sample with the hook that you are using?

> 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
>            Assignee: Bryan Call
>              Labels: api-change
>             Fix For: 5.1.0
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)