[ZCM] [ZC] 2278/ 4 Resolve "Invalid header separators cause ServerProtocolViolation with .NET WebClient/WebRequest"

Issue #2278 Update (Resolve) "Invalid header separators cause ServerProtocolViolation with .NET WebClient/WebRequest"
 Status Resolved, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2278

==============================================================
= Resolve - Entry #4 by mj on Mar 27, 2007 10:00 am

 Status: Accepted => Resolved

ZopeTestCase relies on ZPublisher.HTTPResponse to keep all headers newline seperated. It is ZServer.HTTPResponse's job to output the headers with \r\n.

I fixed bug #2300, which turns out is a dupe of this one, by fixing ZServer's output.

The #2300 fix should cover this bug too, please re-open if this is not the case.
________________________________________
= Comment - Entry #3 by dreamcatcher on Feb 12, 2007 1:08 pm


Uploaded:  "doctest-bodyre.patch"
 - http://www.zope.org/Collectors/Zope/2278/doctest-bodyre.patch/view
The fix breaks an assumption in ZopeTestCase functional doctest package. The following patch adjusts ZopeTestCase to behave appropriately.
________________________________________
= Assign - Entry #2 by ajung on Feb 12, 2007 4:14 am

 Status: Pending => Accepted

 Supporters added: dreamcatcher


________________________________________
= Request - Entry #1 by dreamcatcher on Feb 12, 2007 4:08 am


Uploaded:  "header-separator.patch"
 - http://www.zope.org/Collectors/Zope/2278/header-separator.patch/view
Zope uses '\n' as the header separator in some places, which causes .NET to complain with a ServerProtocolViolation exception. 

The HTTP RFC is not 100% clear if that is a MUST or SHOULD, though it always uses CRLF when referring to headers.

Patch against Zope 2.9
==============================================================