Currently we throw exceptions when non-RFC-compliant HTTP headers are
passed to the setHeaders() method. Following ZF-2019 I did some
thinking, and it seems there is a good reason to allow a non-strict mode
in which users could add their own headers.
What I propose doing is one of the following:
1. Add a configuration option ("strict") to the HTTP Client object
(passed in the constructor or using setConfig()). This option will be
set to true by default - but if set to false, will allow setting
non-strict headers and possibly override some other RFC-compliance
tests.
I think this is the best option.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
