Re: Bugs: mod_php, w3c-libwww, "content-length", "chunked" and RFC 2068
| From: | Sascha Schumann | Date: | Thu, 28 Jun 2001 14:57:20 +0000 |
| Subject: | Re: Bugs: mod_php, w3c-libwww, "content-length", "chunked" and RFC 2068 | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-58343@lists.php.net to get a copy of this message | ||
> mod_php will happily generate messages that include both a content-length
> and a "chunked" transfer encoding *if* a script supplies a
> "content-length" header.
And if it sets "Transfer-Encoding: chunked" as well. PHP
surely does not supply that.
The script author is in (almost) full control of what gets
sent to the wire. PHP does not validate HTTP headers or
performs any kind of checks to ensure that e.g. the
requirements of RFC 2616 are met. It is the author's
responsibility to write correct code which interoperates well
with the defined environment.
- Sascha Experience IRCG
http://schumann.cx/ http://schumann.cx/ircg