[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)
[ 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)
[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)
[ https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875924#comment-13875924 ] Bryan Call commented on TS-1187: I will write a unit test for it and see what happens... > 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: 4.2.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.1.5#6160)
[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)
[ https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586402#comment-13586402 ] James Peach commented on TS-1187: - And if it doesn't set the header, it should return ERROR. > 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
[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)
[ https://issues.apache.org/jira/browse/TS-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586379#comment-13586379 ] Leif Hedstrom commented on TS-1187: --- It sounds like what you want is a TSMimeHdrFieldRename(), I'm moving this out for now. As James points out, it is odd that it works for some headers, but not others. > 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.3.1 > > > 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
[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)
[ 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
[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)
[ 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
