[TS-1125] POST's with Expect: 100-continue are slowed by delayed 100 response.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.2
• Fix Version/s: 5.0.0
• Component/s: HTTP
• Labels: yahoo

Environment

TS 3.0.2 going to Apache 2.2 web server

• Assignee: Bryan Call
• Reporter: William Bardwell
• Created: 01/Mar/12 17:07
• Updated: 15/Jun/15 22:03
• Resolved: 21/May/14 23:23

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.

Issue Links

• is related to: TS-2915 SEGV occurs when POST request was posted without Expect: 100-continue header