You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/02/25 23:32:13 UTC

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

     [ https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-1187:
------------------------------

    Fix Version/s:     (was: 3.3.1)
                   sometime
    
> 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: sometime
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira