Carl Nobile added the comment:
I have run into this same issue. It does violate RFC2616 in section 4.3 "All
1xx (informational), 204 (no content), and 304 (not modified) responses MUST
NOT include a message-body. All other responses do include a message-body,
although it MAY be of
Carl Nobile added the comment:
I was told some time ago that it was documentation changes. And, if I
remember correctly CONTINUE (100) was not ignored, it was actually broken.
Data was being read from stdin when a CONTINUE was received and this should
never happen based on RFC 2616, because
Carl Nobile added the comment:
Yes, exactly. I was not the one who posted the original bug report, but I
found it when I ran into the same problem. I was not exactly sure if the
original poster had the same issues as I had. I do know that my fix to the
code eliminated some code making the code
Carl Nobile added the comment:
André,
As I said I'm not sure if I am fixing the same thing that this bug was
originally posted for. However, after looking at my code I realized that I
just did a quick work around for my situation and it shouldn't be put into
any python release.
Thi
