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

POST's with Expect: 100-continue are slowed by delayed 100 response.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 3.0.2
    • 5.0.0
    • HTTP
    • TS 3.0.2 going to Apache 2.2 web server

    Description

      Sending a post like:
      POST / HTTP/1.1
      Host: www.example.com
      Content-Length: 10
      Expect: 100-continue

      directly to the web server immediately sends back:
      HTTP/1.1 100 Continue

      And then when the post data is sent, a status 200 response comes back.
      But when going through ATS the "HTTP/1.1 100 Continue" is not sent immediately, and instead is sent after the POST data has been received. This is legal, but it makes clients that are hoping for a 100 continue to wait a little while hoping to get that, ATS should forward that response through immediately.

      Note: I see curl using "Expect: 100-continue" with > 1024 bytes of post data, but web searching indicates that some Microsoft products also use it.

      Attachments

        1. ts1125.diff
          11 kB
          Feifei Cai
        2. ts1125.diff
          11 kB
          Bryan Call
        3. ts1125.diff
          11 kB
          Bryan Call
        4. TS-1125.diff
          11 kB
          Feifei Cai
        5. TS-1125.diff
          9 kB
          Feifei Cai

        Issue Links

          Activity

            People

              bcall Bryan Call
              wbardwel William Bardwell
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: