[
https://issues.apache.org/jira/browse/TS-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168541#comment-13168541
]
Leif Hedstrom commented on TS-1045:
-----------------------------------
I'm honestly not sure what the intention was here... There seems to be overlap
for sure. I mean, if TSFetchPageRespGet() returns the full "response", then why
do we need TSFetchRespGet()? That's why I'm wondering that we either
a) Keep only TSFetchPageRespGet(), and expose appropriate APIs to get stuff out
of it.
or
b) Eliminate TSFetchPageRespGet(), and only keep TSFetchRespGet() and a new
TSFetchHdrGet()
Or is there ever a case where we'd need all three ?
> PATCH: add new TSFetchHdrGet API
> --------------------------------
>
> Key: TS-1045
> URL: https://issues.apache.org/jira/browse/TS-1045
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Reporter: James Peach
> Assignee: Leif Hedstrom
> Priority: Minor
> Fix For: 3.1.2
>
> Attachments: 0007-Add-new-public-API-TSFetchHdrGet.patch
>
>
> TSFetchUrl does not provide any way to get the headers from the result. This
> patch adds a new API TSFetchHdrGet(), which is analogous to TSFetchRespGet()
> and returns the headers.
--
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
