| $_POST, $_GET and $_REQUEST discarding duplicates [message #170793] |
Fri, 26 November 2010 23:07  |
 |
James
Messages: 3
Registered: October 2012
Location: India
Karma: 0
|
Junior Member |
|
|
I am working on an application and specifically validating user
input. The application can be sent input via POST or GET. One thing
I need to catch is duplicate variable names being passed:
Take the following string:
myapp.php?a=12&a=12
If I var dump $_REQUEST then or $_GET I get the following ///
array(1) {
["verb"]=>
string(8) "a"
}
The second instance of 'a' is dropped. If I was just using $_GET I
would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
data I don't believe I can do this. Can anybody suggest a function
that will allow me to find this duplicates in in POST and GET data?
I need to do this to pass a series of validation tests, functionally
it has little impact. In an odd side to this if I alter the string to
myapp.php?a=12&a=13 then var_dumping $_REQUEST results in a big fat
null being returned. This I have been able to trap. But duplicate
keys and values have got me stumped.
Any clues?
James J.
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170794 is a reply to message #170793] |
Fri, 26 November 2010 23:34  |
Captain Paralytic
Messages: 204
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On Nov 26, 11:07 pm, James <starr...@gmail.com> wrote:
> I am working on an application and specifically validating user
> input. The application can be sent input via POST or GET. One thing
> I need to catch is duplicate variable names being passed:
>
> Take the following string:
> myapp.php?a=12&a=12
>
> If I var dump $_REQUEST then or $_GET I get the following ///
>
> array(1) {
> ["verb"]=>
> string(8) "a"
>
> }
>
> The second instance of 'a' is dropped. If I was just using $_GET I
> would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
> data I don't believe I can do this. Can anybody suggest a function
> that will allow me to find this duplicates in in POST and GET data?
>
> I need to do this to pass a series of validation tests, functionally
> it has little impact. In an odd side to this if I alter the string to
> myapp.php?a=12&a=13 then var_dumping $_REQUEST results in a big fat
> null being returned. This I have been able to trap. But duplicate
> keys and values have got me stumped.
>
> Any clues?
No guarantees but you could try:
http://www.codediesel.com/php/reading-raw-post-data-in-php/
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170795 is a reply to message #170793] |
Fri, 26 November 2010 23:46 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 11/26/2010 6:07 PM, James wrote:
> I am working on an application and specifically validating user
> input. The application can be sent input via POST or GET. One thing
> I need to catch is duplicate variable names being passed:
>
> Take the following string:
> myapp.php?a=12&a=12
>
> If I var dump $_REQUEST then or $_GET I get the following ///
>
> array(1) {
> ["verb"]=>
> string(8) "a"
> }
>
> The second instance of 'a' is dropped. If I was just using $_GET I
> would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
> data I don't believe I can do this. Can anybody suggest a function
> that will allow me to find this duplicates in in POST and GET data?
>
> I need to do this to pass a series of validation tests, functionally
> it has little impact. In an odd side to this if I alter the string to
> myapp.php?a=12&a=13 then var_dumping $_REQUEST results in a big fat
> null being returned. This I have been able to trap. But duplicate
> keys and values have got me stumped.
>
> Any clues?
Simple - don't use the same name for different values. If you need an
array for your post, use a[]. That way you'll get $_POST[0], $_POST[1],
etc.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170796 is a reply to message #170793] |
Sat, 27 November 2010 07:17 |
Thomas 'PointedEars'
Messages: 701
Registered: October 2010
Karma: 0
|
Senior Member |
|
|
James wrote:
^^^^^
James who?
> I am working on an application and specifically validating user
> input. The application can be sent input via POST or GET. One thing
> I need to catch is duplicate variable names being passed:
Those are not variable names, but parameter names. For variables there
needs to be a *programming* language; (X)HTML is not.
> Take the following string:
> myapp.php?a=12&a=12
>
> If I var dump $_REQUEST then or $_GET I get the following ///
>
> array(1) {
> ["verb"]=>
> string(8) "a"
> }
>
> The second instance of 'a' is dropped. If I was just using $_GET I
> would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
> data I don't believe I can do this. Can anybody suggest a function
> that will allow me to find this duplicates in in POST and GET data?
No.
<… name="verb[]" …>
will get you
array(1) {
["verb"]=>
array(…) {
…
}
}
It is a very old "problem", to be found discussed in a great many PHP FAQs.
Please do search next time.
PointedEars
--
Danny Goodman's books are out of date and teach practices that are
positively harmful for cross-browser scripting.
-- Richard Cornford, cljs, <cife6q$253$1$8300dec7(at)news(dot)demon(dot)co(dot)uk> (2004)
|
|
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170799 is a reply to message #170795] |
Sat, 27 November 2010 12:47 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 11/26/2010 6:46 PM, Jerry Stuckle wrote:
> On 11/26/2010 6:07 PM, James wrote:
>> I am working on an application and specifically validating user
>> input. The application can be sent input via POST or GET. One thing
>> I need to catch is duplicate variable names being passed:
>>
>> Take the following string:
>> myapp.php?a=12&a=12
>>
>> If I var dump $_REQUEST then or $_GET I get the following ///
>>
>> array(1) {
>> ["verb"]=>
>> string(8) "a"
>> }
>>
>> The second instance of 'a' is dropped. If I was just using $_GET I
>> would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
>> data I don't believe I can do this. Can anybody suggest a function
>> that will allow me to find this duplicates in in POST and GET data?
>>
>> I need to do this to pass a series of validation tests, functionally
>> it has little impact. In an odd side to this if I alter the string to
>> myapp.php?a=12&a=13 then var_dumping $_REQUEST results in a big fat
>> null being returned. This I have been able to trap. But duplicate
>> keys and values have got me stumped.
>>
>> Any clues?
>
> Simple - don't use the same name for different values. If you need an
> array for your post, use a[]. That way you'll get $_POST[0], $_POST[1],
> etc.
>
Correction - that should be $_POST['a'][0], $_POST['a'][1], etc.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170801 is a reply to message #170796] |
Sat, 27 November 2010 15:32 |
Magno
Messages: 49
Registered: October 2010
Karma: 0
|
Member |
|
|
On 11/27/2010 04:17 AM, Thomas 'PointedEars' Lahn wrote:
> James wrote:
> ^^^^^
> James who?
Your business?
> ...
> It is a very old "problem", to be found discussed in a great many PHP FAQs.
> Please do search next time.
>
>
> PointedEars
Please, quit that arrogant attitude and please don’t post if you have no
real contribution to do. Because of trolls is why newbies are constantly
abandoning usenet as soon as they are replied.
(Also, put your signature appropriately)
....
James, this Pointedears is a troll so don’t take personally his
condescendant attitude against others.
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170802 is a reply to message #170801] |
Sat, 27 November 2010 16:58 |
Luuk
Messages: 329
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 27-11-10 16:32, Magno wrote:
> On 11/27/2010 04:17 AM, Thomas 'PointedEars' Lahn wrote:
>> James wrote:
>> ^^^^^
>> James who?
>
> Your business?
>
>> ...
>> It is a very old "problem", to be found discussed in a great many PHP
>> FAQs.
>> Please do search next time.
>>
>>
>> PointedEars
>
> Please, quit that arrogant attitude and please don’t post if you have no
> real contribution to do. Because of trolls is why newbies are constantly
> abandoning usenet as soon as they are replied.
> (Also, put your signature appropriately)
>
> ...
>
> James, this Pointedears is a troll so don’t take personally his
> condescendant attitude against others.
Who is being arrogant here ?
and, yes, Thomas was wrong (at least this time...)
--
Luuk
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170803 is a reply to message #170796] |
Sat, 27 November 2010 17:05 |
Luuk
Messages: 329
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 27-11-10 08:17, Thomas 'PointedEars' Lahn wrote:
> James wrote:
> ^^^^^
> James who?
>
>> I am working on an application and specifically validating user
>> input. The application can be sent input via POST or GET. One thing
>> I need to catch is duplicate variable names being passed:
>
> Those are not variable names, but parameter names. For variables there
> needs to be a *programming* language; (X)HTML is not.
>
>> Take the following string:
>> myapp.php?a=12&a=12
>>
>> If I var dump $_REQUEST then or $_GET I get the following ///
>>
>> array(1) {
>> ["verb"]=>
>> string(8) "a"
>> }
>>
>> The second instance of 'a' is dropped. If I was just using $_GET I
>> would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
>> data I don't believe I can do this. Can anybody suggest a function
>> that will allow me to find this duplicates in in POST and GET data?
>
> No.
>
> <… name="verb[]" …>
>
> will get you
>
> array(1) {
> ["verb"]=>
> array(…) {
> …
> }
> }
>
> It is a very old "problem", to be found discussed in a great many PHP FAQs.
> Please do search next time.
>
>
> PointedEars
Can you point us to these FAQ's?
When i tested, i got the following response:
test.php?a=12&a=12
response:
array(1) { ["a"]=> string(2) "12" }
so, OP seems to be right that the second parameter gets dropped.
but when i test with:
test.php?a=12&a=13
i get:
array(1) { ["a"]=> string(2) "13" }
so, in fact it looks more like the last parameters survives....
--
Luuk
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170804 is a reply to message #170802] |
Sat, 27 November 2010 18:41 |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 11/27/2010 11:58 AM, Luuk wrote:
> On 27-11-10 16:32, Magno wrote:
>> On 11/27/2010 04:17 AM, Thomas 'PointedEars' Lahn wrote:
>>> James wrote:
>>> ^^^^^
>>> James who?
>>
>> Your business?
>>
>>> ...
>>> It is a very old "problem", to be found discussed in a great many PHP
>>> FAQs.
>>> Please do search next time.
>>>
>>>
>>> PointedEars
>>
>> Please, quit that arrogant attitude and please don’t post if you have no
>> real contribution to do. Because of trolls is why newbies are constantly
>> abandoning usenet as soon as they are replied.
>> (Also, put your signature appropriately)
>>
>> ...
>>
>> James, this Pointedears is a troll so don’t take personally his
>> condescendant attitude against others.
>
> Who is being arrogant here ?
>
Pointed Ears is. Mango is just pointing out PE's normal behavior to an
unsuspecting person.
> and, yes, Thomas was wrong (at least this time...)
>
>
>
He virtually always is, unless it's something he can copy/paste. And
not just in this newsgroup.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170805 is a reply to message #170804] |
Sat, 27 November 2010 18:51 |
Luuk
Messages: 329
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
On 27-11-10 19:41, Jerry Stuckle wrote:
> On 11/27/2010 11:58 AM, Luuk wrote:
>> On 27-11-10 16:32, Magno wrote:
>>> On 11/27/2010 04:17 AM, Thomas 'PointedEars' Lahn wrote:
>>>> James wrote:
>>>> ^^^^^
>>>> James who?
>>>
>>> Your business?
>>>
>>>> ...
>>>> It is a very old "problem", to be found discussed in a great many PHP
>>>> FAQs.
>>>> Please do search next time.
>>>>
>>>>
>>>> PointedEars
>>>
>>> Please, quit that arrogant attitude and please don’t post if you have no
>>> real contribution to do. Because of trolls is why newbies are constantly
>>> abandoning usenet as soon as they are replied.
>>> (Also, put your signature appropriately)
>>>
>>> ...
>>>
>>> James, this Pointedears is a troll so don’t take personally his
>>> condescendant attitude against others.
>>
>> Who is being arrogant here ?
>>
>
> Pointed Ears is. Mango is just pointing out PE's normal behavior to an
> unsuspecting person.
>
>> and, yes, Thomas was wrong (at least this time...)
>>
>>
>>
>
> He virtually always is, unless it's something he can copy/paste. And not
> just in this newsgroup.
>
>
I was expecting a reply from this other 'arrogant' one...
Sigh, WHEN do people grow up....?
or, to speak with Jerry Stuckle,
This last post has NOTHING TO DO WITH comp.lang.php, .....
*We* should never post articles like this!
--
Luuk
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170806 is a reply to message #170803] |
Sat, 27 November 2010 18:53 |
Michael Fesser
Messages: 215
Registered: September 2010
Karma: 0
|
Senior Member |
|
|
.oO(Luuk)
> On 27-11-10 08:17, Thomas 'PointedEars' Lahn wrote:
>>
>> <… name="verb[]" …>
>>
>> will get you
>>
>> array(1) {
>> ["verb"]=>
>> array(…) {
>> …
>> }
>> }
>>
>> It is a very old "problem", to be found discussed in a great many PHP FAQs.
>> Please do search next time.
>
> Can you point us to these FAQ's?
See questions 3 and 4 on
http://www.php.net/manual/en/faq.html.php
> When i tested, i got the following response:
>
> test.php?a=12&a=12
>
> response:
> array(1) { ["a"]=> string(2) "12" }
>
> so, OP seems to be right that the second parameter gets dropped.
No.
> but when i test with:
> test.php?a=12&a=13
>
> i get:
>
> array(1) { ["a"]=> string(2) "13" }
>
> so, in fact it looks more like the last parameters survives....
Correct, because the second value overrides the first one. If you want
to receive both in your script, make them an array with the syntax
already mentioned.
Micha
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170807 is a reply to message #170805] |
Sat, 27 November 2010 19:05 |
Magno
Messages: 49
Registered: October 2010
Karma: 0
|
Member |
|
|
On 11/27/2010 03:51 PM, Luuk wrote:
> On 27-11-10 19:41, Jerry Stuckle wrote:
>> On 11/27/2010 11:58 AM, Luuk wrote:
>>> On 27-11-10 16:32, Magno wrote:
>>>> On 11/27/2010 04:17 AM, Thomas 'PointedEars' Lahn wrote:
>>>> > James wrote:
>>>> > ^^^^^
>>>> > James who?
>>>>
>>>> Your business?
>>>>
>>>> > ...
>>>> > It is a very old "problem", to be found discussed in a great many PHP
>>>> > FAQs.
>>>> > Please do search next time.
>>>> >
>>>> >
>>>> > PointedEars
>>>>
>>>> Please, quit that arrogant attitude and please don’t post if you
>>>> have no
>>>> real contribution to do. Because of trolls is why newbies are
>>>> constantly
>>>> abandoning usenet as soon as they are replied.
>>>> (Also, put your signature appropriately)
>>>>
>>>> ...
>>>>
>>>> James, this Pointedears is a troll so don’t take personally his
>>>> condescendant attitude against others.
>>>
>>> Who is being arrogant here ?
>>>
>>
>> Pointed Ears is. Mango is just pointing out PE's normal behavior to an
>> unsuspecting person.
>>
>>> and, yes, Thomas was wrong (at least this time...)
>>>
>>>
>>>
>>
>> He virtually always is, unless it's something he can copy/paste. And not
>> just in this newsgroup.
>>
>>
>
> I was expecting a reply from this other 'arrogant' one...
>
> Sigh, WHEN do people grow up....?
>
> or, to speak with Jerry Stuckle,
>
> This last post has NOTHING TO DO WITH comp.lang.php, .....
>
> *We* should never post articles like this!
>
?????????
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170809 is a reply to message #170806] |
Sun, 28 November 2010 16:55 |
|
James
Messages: 3
Registered: October 2012
Location: India
Karma: 0
|
Junior Member |
|
|
>> When i tested, i got the following response:
>
>> test.php?a=12&a=12
>
>> response:
>> array(1) { ["a"]=> string(2) "12" }
>
>> so, OP seems to be right that the second parameter gets dropped.
>
> No.
>
>> but when i test with:
>> test.php?a=12&a=13
>
>> i get:
>
>> array(1) { ["a"]=> string(2) "13" }
>
>> so, in fact it looks more like the last parameters survives....
>
> Correct, because the second value overrides the first one. If you want
> to receive both in your script, make them an array with the syntax
> already mentioned.
>
> Micha
It seems to be inconsistent across versions now testing it. Either
way I have no control over what comes in -- this is a OAI-PMH
repository (http://www.openarchives.org/OAI/openarchivesprotocol.html)
- I have no control over the harvesting services, forms or any HTML -
I don't get into any of that. All I can do is try and make sure that
the input I receive is valid and that I move forwards from there. I
doubt any HTML forms are used anywhere in this process, its either
query strings, or post via applications written in Pearl, C etc etc
and I have no control over poorly written harvesters.
oaipmh.php?verb=Identify (this is entirely valid.)
oaipmh.php?verb=Identify&verb=ListMetadataFormats (Invalid)
oaipmh.php?verb=Identify&verb=Invalid (Invalid)
The latter two seem impossible to catch via $_POST, $_GET and
$_REQUEST ... given that I have no form control.
Just trying to make things perfect here, as this is part of the
validation tests. I am going to pass the query strings our manually,
and interrogate the raw post data I think.
James J.
|
|
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170819 is a reply to message #170809] |
Mon, 29 November 2010 05:43 |
Jeff North
Messages: 58
Registered: November 2010
Karma: 0
|
Member |
|
|
On Sun, 28 Nov 2010 08:55:34 -0800 (PST), in comp.lang.php James
<starritt(at)gmail(dot)com>
<09c3a650-a28b-4a14-8b73-5feeb8e2ed38(at)p7g2000prb(dot)googlegroups(dot)com>
wrote:
> | > >When i tested, i got the following response:
> | >
> | > >test.php?a=12&a=12
> | >
> | > >response:
> | > >array(1) { ["a"]=> string(2) "12" }
> | >
> | > >so, OP seems to be right that the second parameter gets dropped.
> | >
> | > No.
> | >
> | > >but when i test with:
> | > >test.php?a=12&a=13
> | >
> | > >i get:
> | >
> | > >array(1) { ["a"]=> string(2) "13" }
> | >
> | > >so, in fact it looks more like the last parameters survives....
> | >
> | > Correct, because the second value overrides the first one. If you want
> | > to receive both in your script, make them an array with the syntax
> | > already mentioned.
> | >
> | > Micha
> |
> | It seems to be inconsistent across versions now testing it. Either
> | way I have no control over what comes in -- this is a OAI-PMH
> | repository (http://www.openarchives.org/OAI/openarchivesprotocol.html)
> | - I have no control over the harvesting services, forms or any HTML -
> | I don't get into any of that. All I can do is try and make sure that
> | the input I receive is valid and that I move forwards from there. I
> | doubt any HTML forms are used anywhere in this process, its either
> | query strings, or post via applications written in Pearl, C etc etc
> | and I have no control over poorly written harvesters.
> |
> |
> | oaipmh.php?verb=Identify (this is entirely valid.)
> | oaipmh.php?verb=Identify&verb=ListMetadataFormats (Invalid)
> | oaipmh.php?verb=Identify&verb=Invalid (Invalid)
> |
> | The latter two seem impossible to catch via $_POST, $_GET and
> | $_REQUEST ... given that I have no form control.
> |
> | Just trying to make things perfect here, as this is part of the
> | validation tests. I am going to pass the query strings our manually,
> | and interrogate the raw post data I think.
You can always use $_SERVER['QUERY_STRING'] to grab the info (for GET
data anyway). The problem is that you will need to do the parsing of
the string yourself. Not too hard to do. I think the php site even has
code to do this.
|
|
|
|
| Re: $_POST, $_GET and $_REQUEST discarding duplicates [message #170820 is a reply to message #170793] |
Mon, 29 November 2010 14:12 |
matt[1]
Messages: 40
Registered: September 2010
Karma: 0
|
Member |
|
|
On Fri, 26 Nov 2010 15:07:33 -0800, James wrote:
> I am working on an application and specifically validating user input.
> The application can be sent input via POST or GET. One thing I need to
> catch is duplicate variable names being passed:
>
> Take the following string:
> myapp.php?a=12&a=12
This doesn't match...
> If I var dump $_REQUEST then or $_GET I get the following ///
>
> array(1) {
> ["verb"]=>
> string(8) "a"
> }
....this. Where's "verb" in your URI? Make sure you're posting real
examples. If this is real, it looks like something external is re-
arranging your request variables in ways that we cannot predict.
> The second instance of 'a' is dropped. If I was just using $_GET I
> would simply pull $_SERVER['QUERY_STRING] up and pass it but for POST
> data I don't believe I can do this. Can anybody suggest a function that
> will allow me to find this duplicates in in POST and GET data?
Well, you have two options--you can either use the PHP-method of passing
multiple values to the same parameter name:
myapp.php?a[]=12&a[]=12
which will yield a two-element array, or if that's not an option, you can
parse the URI yourself using $_SERVER variables.
> I need to do this to pass a series of validation tests, functionally it
> has little impact. In an odd side to this if I alter the string to
> myapp.php?a=12&a=13 then var_dumping $_REQUEST results in a big fat null
> being returned. This I have been able to trap. But duplicate keys and
> values have got me stumped.
$_REQUEST should not === null in this case. Methinks something (in your
function library perhaps) is mucking with your variables before your
testing.
> Any clues?
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]