The handle_expect_100() implementation in BaseHTTPRequestHandler currently calls send_response_only(100) followed by flush_headers(). However, even a 1xx response is always followed by a (potentially empty) set of response headers (cf. http://tools.ietf.org/html/rfc2616#section-9.9). Therefore, clients will block waiting for an additional '\r\n' before sending the buffer.

The attached patch fixes the problem.

The correct link is http://tools.ietf.org/html/rfc2616#section-10.1:

10.1 Informational 1xx

   This class of status code indicates a provisional response,
   consisting only of the Status-Line and optional headers, and is
   terminated by an empty line.
   [...]

Currently handle_expect_100() does not send this empty line.

*ping*

Is there anything wrong with the patch? What do I have to do to get it applied?

A test would be good.

Thanks for looking at this! Attached is an updated patch with testcase (sorry, I thought I had included testcases everywhere).

New changeset 093ab6c02ff4 by Benjamin Peterson in branch '3.3':
fix handling of 100-continue status code (closes #18574)
http://hg.python.org/cpython/rev/093ab6c02ff4

New changeset 20a2597d6653 by Benjamin Peterson in branch 'default':
merge 3.3 (#18574)
http://hg.python.org/cpython/rev/20a2597d6653

I just realized that the Misc/NEWS entry is just utterly wrong (it is talking abou the client, even though the bug is in the server), my apologies. Here's a fixed one:

- Issue #18574: Added missing newline in 100-Continue reply from
  http.server.BaseHTTPRequestHandler. Patch by Nikolaus Rath.

New changeset d00ed6e7a823 by Benjamin Peterson in branch '3.3':
correct news entry for #18574
http://hg.python.org/cpython/rev/d00ed6e7a823

New changeset cf0678c3b735 by Benjamin Peterson in branch 'default':
merge 3.3 (#18574)
http://hg.python.org/cpython/rev/cf0678c3b735