Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-1062

Introduce extended FetchSM API

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0
    • Component/s: TS API
    • Labels:
      None

      Description

      1) Introduce extended FetchSM APIs, which will be used by SPDY.

      2) Make TSFetchUrl() dechunk encoding automatically:
      If you use TSFetchUrl() to fetch a resource and the response comes back with chunked encoding, you are basically hosed. The caller never gets the SUCCESS event because FetchSM does not know how to decode the body. There's no content-length header and the origin server doesn't drop the TCP connection, so we just sit there waiting for the response to finish forever (well until the origin server drops the connection 10s later).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                yunkai Yunkai Zhang
                Reporter:
                jamespeach James Peach
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: