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 2016/04/17 20:23:25 UTC

[jira] [Updated] (TS-4351) FetchSM shouldn't expose unprotected response headers

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

Leif Hedstrom updated TS-4351:
------------------------------
    Fix Version/s: sometime

> FetchSM shouldn't expose unprotected response headers
> -----------------------------------------------------
>
>                 Key: TS-4351
>                 URL: https://issues.apache.org/jira/browse/TS-4351
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cleanup
>            Reporter: Masakazu Kitajo
>             Fix For: sometime
>
>
> {{FetchSM}} exposes a member variable {{HTTPHdr client_response_hdr}} and anybody can modify headers in it. However, such modification breaks {{FetchSM}}'s internal state, and it results unexpected behavior.
> To avoid such modification, {{client_response_hdr}} shouldn't be exposed directly and {{FetchSM}} should have a getter which returns the headers with {{const}} modifier.
> It sounds easy but we need to fix an other issue (TS-4350) first, because operations against {{const HTTPHdr}} are limited unreasonably.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)