Uwe Schindler wrote:
> What we need is:
> 2) a function to simply set the status code without changing anything other.
There's a (external) function:
http://php.net/manual/en/function.http-send-status.php
...and for the unlucky:
header("Dummy:", true, $status_code);
But if your patch makes sen
> -Original Message-
> From: Rasmus Lerdorf [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 01, 2007 2:22 AM
> To: Oliver Block
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] Setting HTTP results code vs. HTTP type
>
> Oliver Block wrote:
> > Am Diens
Am Dienstag, 1. Mai 2007 02:22 schrieb Rasmus Lerdorf:
> Oliver Block wrote:
> And note that I only said it was fine to respond
> with a 1.1 reply, that doesn't mean it is fine to send an encoding the
> client doesn't support.
Well.
Regards,
Oliver
--
PHP Internals - PHP Runtime Development Ma
Uwe Schindler wrote:
* Some scripts use header('HTTP/1.0 301 Moved Permanently'). Problem here:
You must supply a HTTP version (this seems to be a problem in Apache), and
This is not necessarily a problem with Apache, it is just a problem in
the current implementation as far as I can tell. If
> - Update the PHP header() documentation to mention this. I was also
> thinking that supporting/documenting header(null, true, 404); or the
> like would be nice for people who only want to set the return code and
> leave the HTTP type unchanged.
I think this would bet he best approach, to give th
Rasmus Lerdorf wrote:
Go read the archives. And note that I only said it was fine to respond
with a 1.1 reply, that doesn't mean it is fine to send an encoding the
client doesn't support.
That's why I think PHP shouldn't mess with the proto_num field or
otherwise upgrade the HTTP version of
Oliver Block wrote:
Am Dienstag, 1. Mai 2007 01:49 schrieb Rasmus Lerdorf:
This came up many times on the Apache lists years ago, and Roy Fielding
who wrote that spec repeatedly said it was fine to reply with a 1.1
response to a 1.0 request.
Did he give any rationale for his view?
Go read
Am Dienstag, 1. Mai 2007 01:49 schrieb Rasmus Lerdorf:
> This came up many times on the Apache lists years ago, and Roy Fielding
> who wrote that spec repeatedly said it was fine to reply with a 1.1
> response to a 1.0 request.
Did he give any rationale for his view?
Regards,
Oliver
--
PHP I
Hello Rasmus,
Am Dienstag, 1. Mai 2007 01:05 schrieb Rasmus Lerdorf:
> Replying to a 1.0 request with a 1.1 response is perfectly fine.
I doubt that it is standard conformant. HTTP/1.0 doesn't
even know chunked data (RFC1945).
Best Regards,
Oliver
--
PHP Internals - PHP Runtime Development M
Christian Schneider wrote:
Christian Schneider wrote:
version for which the server is at least conditionally compliant, and
whose major version is less than or equal to the one received in the
request."
Oops, missed the "major" version part there. Sorry for that, should read
things more care
Christian Schneider wrote:
version for which the server is at least conditionally compliant, and
whose major version is less than or equal to the one received in the
request."
Oops, missed the "major" version part there. Sorry for that, should read
things more carefully, especially at 1:30am
Rasmus Lerdorf wrote:
Replying to a 1.0 request with a 1.1 response is perfectly fine.
It is the default for a fresh Apache install on a request for a
simple static file, for example.
This seems bogus to me.
Quoting from the very last line of the HTTP RFC 3.6 Transfer Codings:
http://www.w3.or
Replying to a 1.0 request with a 1.1 response is perfectly fine.
It is the default for a fresh Apache install on a request for a
simple static file, for example.
-Rasmus
Christian Schneider wrote:
Hi all,
I ran into the following problem I would like to get an opinion on: We
noticed that our we
Hi all,
I ran into the following problem I would like to get an opinion on: We
noticed that our website returns a HTTP/1.1 chunked response even when
the request was a HTTP/1.0 request (e.g. php file_get_contents).
What happens:
- Wordpress (wrongly) set the result code with a hardcoded
@h
14 matches
Mail list logo
