I've always assumed it was for security.
Imagine something like:
Realistically, if you tried to access the value as a string, you would
get "Array" either way. But I still wouldn't want users to be able to
"pollute" $_FILES for people who were assuming a non-array upload.
The way it is no
On Thu, February 8, 2007 5:15 pm, Brian Moon wrote:
> Darrel O'Pry wrote:
>> I was wondering if anyone could point me to a resource explaining
>> why
>> the _FILES array is structured as it is with html arrays.
>
> What is an html array?
I believe he means HTTP array such as $_GET $_POST $_REQUEST
generates $_GET['foo'][0..n]
generates
$_FILES['foo']['tmp_name/name/etc'][0..n]
I think this could pretty much be considered an inconsistence but
changing wouldn't possible due to the BC demon awakening and wreaking
havoc upon doing so.
V
Darrel O'Pry wrote:
On Thu, 2007-02-08 at 17:15
On Thu, 2007-02-08 at 17:15 -0600, Brian Moon wrote:
> Darrel O'Pry wrote:
> > I was wondering if anyone could point me to a resource explaining why
> > the _FILES array is structured as it is with html arrays.
>
> What is an html array?
Maybe that is not the correct diction. I picked it up somew
Darrel O'Pry wrote:
I was wondering if anyone could point me to a resource explaining why
the _FILES array is structured as it is with html arrays.
What is an html array?
--
Brian Moon
-
http://dealnews.com/
It's good to be cheap =)
--
PHP Internals - PHP Runtime Development Mail
I was wondering if anyone could point me to a resource explaining why
the _FILES array is structured as it is with html arrays. I've been
googling and reading rfc1867.c and finding very little explanation.
The _FILES[$key]['temp_name'][$key] is quite awkward when dealing with
multiple uploads.
I
