>> 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 responsibility.
>
> No. Sending misspelled hearders only affects the current request.
> Sending content in a situation where no content
On Sun, 2006-11-12 at 15:26 +, [EMAIL PROTECTED] wrote:
> > 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 out
On Sun, Nov 12, 2006 at 03:21:36PM +0100, Thijs Kinkhorst wrote:
> severity 388443 wishlist
> forwarded 388443 http://issues.apache.org/bugzilla/show_bug.cgi?id=40953
> thanks
>
> Hi,
>
> Christoph Biedl wrote:
> > > >
> > > > | > > > | header('HTTP/1.0 304 Not Modified');
> > > > | ?>
> > >
>
severity 388443 wishlist
forwarded 388443 http://issues.apache.org/bugzilla/show_bug.cgi?id=40953
thanks
Hi,
Christoph Biedl wrote:
> > >
> > > | > > | header('HTTP/1.0 304 Not Modified');
> > > | ?>
> >
> > While I can see the argument that apache should perhaps be trimming its
>
> See the R
"be conservative in what you do, be liberal in what you accept from others"
-- Jon Postel
In other words, the bug is in both apache and the php scripts
-Tim
On 9/24/06, Florian Weimer <[EMAIL PROTECTED]> wrote:
* Christoph Biedl:
> This would result in a lot of bug reports against the accord
* Christoph Biedl:
> This would result in a lot of bug reports against the according scripts.
But this is the way to go, I'm afraid. Or something could be
implemented at the PHP level, I guess. If it's only possible to get a
conforming 304 reply by stripping the trailing newline from the .php
f
Christoph Biedl wrote:
>
> | | header('HTTP/1.0 304 Not Modified');
> | ?>
While I can see the argument that apache should perhaps be trimming its
own output, you are aware that you can "fix" this in your PHP script by
not having that trailing newline in the file, right?
I realise some text edi
Adam Conrad wrote...
> Christoph Biedl wrote:
> >
> > | > | 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".
> own output, you are aware that you can "
Package: apache2
Version: 2.0.55-4.1
Severity: normal
Tags: upstream
A php script may set the http reply code to 304 i.e. "not modified".
Then Apache happily forwards that code to the caller and also all other
data supplied by that script, for example:
|
| Hello World
[ foo.php ]
yields
| $ te
9 matches
Mail list logo
