[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#388443: apache2: MUST NOT send data in an 304 reply

severity 388443 wishlist
forwarded 388443 http://issues.apache.org/bugzilla/show_bug.cgi?id=40953


Christoph Biedl wrote:
> > > 
> > > | <?php
> > > | header('HTTP/1.0 304 Not Modified');
> > > | ?>
> > 
> > While I can see the argument that apache should perhaps be trimming its
> See the RfC. It is not "apache should perhaps", it is "apache must".

I disagree with your interpretation of the RFC here. I think it's
"apache should" and "the script must" in this case. When Apache runs a
CGI or PHP script, it essentially passes off the responsibility of
RFC-compliant output on to the script in question. There's many other
incompliant things, like misspelled headers, a script can send, but
Apache doesn' stop it from doing that. It's ultimately the script's

It could, of course. But that's wishlist. I've filed such a request for
enhancement upstream.


Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: