Hi,
for debugging i'd use var_dump, which doesn't output ambiguous things.
Regards,
Stefan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (632 total including feature requests)
===[*Directory/Filesystem functions]
40661 Open cwd is reset when shutdown handler runs
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (43 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
27372 Verified parse error
hello,
the cvs web interface gives the following revision information for file
mysqli_fe.c. In short
Branch PHP_5_1: Revision 1.49.2.6
Branch PHP_5_2: Revision 1.49.2.5.2.1
If I understand it right, PHP_5_2 should be the later one!?
Regards,
Oliver
--
PHP Internals - PHP Runtime
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
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
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:
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
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
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
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
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
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
13 matches
Mail list logo
