You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Naveen (JIRA)" <ji...@apache.org> on 2011/06/02 05:38:47 UTC

[jira] [Updated] (TS-817) TSFetchUrl/TSFetchPages does not work with HTTP/1.1 requests

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

Naveen updated TS-817:
----------------------

         Labels: api-change function  (was: api-change)
       Priority: Major  (was: Minor)
    Description: The API calls TSFetchUrl/TSFetchPages do not work with HTTP/1.1 requests. The implementation seems to use the "end of the connection" to signal the user callback function, which is not the case on persistent connections.  (was: The api calls TSFetchUrl/TSFetchPages do not work with HTTP/1.1 requests. They use the end of the connection to signal the user continuation, which is not the case on persistent connections.)

> TSFetchUrl/TSFetchPages does not work with HTTP/1.1 requests
> ------------------------------------------------------------
>
>                 Key: TS-817
>                 URL: https://issues.apache.org/jira/browse/TS-817
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>    Affects Versions: 2.1.9, 2.1.8
>            Reporter: Naveen
>              Labels: api-change, function
>
> The API calls TSFetchUrl/TSFetchPages do not work with HTTP/1.1 requests. The implementation seems to use the "end of the connection" to signal the user callback function, which is not the case on persistent connections.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira