I posted in the pecl-dev malling list, the intention of publishing a new php
extension. And Pierre suggested to make it available in the php.net cvs.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 16, 2008, at 11:55 , Stanislav Malyshev wrote:
I dont understand the problem. You use request if you do not care
where a parameter is set and you use the other superglobals when
you do care.
The problem is that variables_order should specify what gets into
_REQUEST (as documented
I dont understand the problem. You use request if you do not care where
a parameter is set and you use the other superglobals when you do care.
The problem is that variables_order should specify what gets into
_REQUEST (as documented in the manual) and as Stefan reports it doesn't
exactly do
I would like to assist the Doc team in improving the PHP documentation,
particularly in some of the lesser used and newer extensions.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 16, 2008, at 9:17 , Stefan Esser wrote:
Stanislav Malyshev schrieb:
@Richard: You don't understand the Problem with _REQUEST. It is not
about the fact that someone can forge GET, POST; COOKIE variables.
It is about the fact that COOKIEs will overwrite GET and POST data
in
REQUEST.
Changing the variables_order to CGP is not a good idea either, because
then applications that use cookies through _REQUEST could be tricked by
I can imagine why one would use _REQUEST to work with GET and POST
alike. However I can not imagine what would be the reason to use REQUEST
if you need
Stanislav Malyshev schrieb:
>> @Richard: You don't understand the Problem with _REQUEST. It is not
>> about the fact that someone can forge GET, POST; COOKIE variables.
>> It is about the fact that COOKIEs will overwrite GET and POST data in
>> REQUEST.
>
> Isn't it solved by setting variables_orde
Stanislav Malyshev wrote:
@Richard: You don't understand the Problem with _REQUEST. It is not
about the fact that someone can forge GET, POST; COOKIE variables.
It is about the fact that COOKIEs will overwrite GET and POST data in
REQUEST.
Isn't it solved by setting variables_order to correct v
@Richard: You don't understand the Problem with _REQUEST. It is not
about the fact that someone can forge GET, POST; COOKIE variables.
It is about the fact that COOKIEs will overwrite GET and POST data in
REQUEST.
Isn't it solved by setting variables_order to correct value, at least
partially?
