«

Considering a multipart/form-data form, is there a formula to calculate
the size of an uploaded file from within $ENV{'CONTENT_LENGTH'} which
represent the size of the entire data in STDIN (including all name/value
pairs, boundary between parts, content-disposition & type lines, some
blank lines) ?

Asterbing <> wrote:
> Considering a multipart/form-data form, is there a formula to calculate
> the size of an uploaded file from within $ENV{'CONTENT_LENGTH'} which
> represent the size of the entire data in STDIN (including all name/value
> pairs, boundary between parts, content-disposition & type lines, some
> blank lines) ?

No.

Xho

--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB

Asterbing <> wrote:

> Considering a multipart/form-data form, is there a formula to calculate
> the size of an uploaded file from within $ENV{'CONTENT_LENGTH'} which
> represent the size of the entire data in STDIN (including all name/value
> pairs, boundary between parts, content-disposition & type lines, some
> blank lines) ?

Why not -s filename assuming you store it in a file system?

--
John Bokma Freelance software developer
&
Experienced Perl programmer: http://castleamber.com/

In article <Xns97AA6D15AEC7Fcastleamber@130.133.1.4>,
says...
> Why not -s filename assuming you store it in a file system?
>

Because I would like to avoid too big files

In article <20060419114637.129$>,
says...
>
> No.
>

Why ?

Asterbing <> wrote:

> In article <Xns97AA6D15AEC7Fcastleamber@130.133.1.4>,
> says...
>> Why not -s filename assuming you store it in a file system?
>
> Because I would like to avoid too big files

Ok, so your question actually is: how do I avoid the uploading of big
files:

$CGI:OST_MAX

If set to a non-negative integer, this variable puts a ceiling on the
size of POSTings, in bytes. If CGI.pm detects a POST that is greater than
the ceiling, it will immediately exit with an error message. This value
will affect both ordinary POSTs and multipart POSTs, meaning that it
limits the maximum size of file uploads as well. You should set this to a
reasonably high value, such as 1 megabyte.


(documentation of CGI.pm, Avoiding Denial of Service Attacks)

--
John Bokma Freelance software developer
&
Experienced Perl programmer: http://castleamber.com/

John Bokma <> wrote:
> Asterbing <> wrote:
>
> > In article <Xns97AA6D15AEC7Fcastleamber@130.133.1.4>,
> > says...
> >> Why not -s filename assuming you store it in a file system?
> >
> > Because I would like to avoid too big files
>
> Ok, so your question actually is: how do I avoid the uploading of big
> files:
>
> $CGI:OST_MAX
>
> If set to a non-negative integer, this variable puts a ceiling on the
> size of POSTings, in bytes. If CGI.pm detects a POST that is greater than
> the ceiling, it will immediately exit with an error message.

That should probaby be changed. It does not immediately exit with
an error message. It first reads (and discards) the entire contents
of the POST, which apparently the OP doesn't want to happen althought it
is kind of hard to figure out exactly what he wants. Also, it doesn't
exit at all. It causes param to return an empty param list, and it causes
cgi_error to return an error message--no exiting involved.

Xho

--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB

Asterbing <> wrote:
> In article <20060419114637.129$>,
> says...
> >
> > No.
> >
>
> Why ?

Why isn't the moon made out of green cheese?

You pretty much covered why in the post. You can't figure out how the
sizes of the different parts of the post (which sum up to CONTENT_LENGTH)
are distributed until you read all but one of them. Since you can't
gaurantee that the part which contains the file upload is the last part,
you can't figure out how big that part is until you have read it.

I have no idea why you think you need to do this.....

Xho

--
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service $9.95/Month 30GB

In article <20060419144430.442$>,
says...
> I have no idea why you think you need to do this.....
>

Because when CONTENT_LENGTH has been informed by server itself after
receiving of entire POST, I can effectively read STDIN, extract uploaded
data and do the substraction.

But, when CONTENT_LENGTH comes from original request, how to proceed ?

Say, I wish to avoid any upload (I mean write on server, since data may
already be in STDIN) above 1MB, how to proceed ?

wrote:

> John Bokma <> wrote:
>> Asterbing <> wrote:
>>
>> > In article <Xns97AA6D15AEC7Fcastleamber@130.133.1.4>,
>> > says...
>> >> Why not -s filename assuming you store it in a file system?
>> >
>> > Because I would like to avoid too big files
>>
>> Ok, so your question actually is: how do I avoid the uploading of big
>> files:
>>
>> $CGI:OST_MAX
>>
>> If set to a non-negative integer, this variable puts a ceiling on
>> the
>> size of POSTings, in bytes. If CGI.pm detects a POST that is greater
>> than the ceiling, it will immediately exit with an error message.
>
> That should probaby be changed. It does not immediately exit with
> an error message. It first reads (and discards) the entire contents
> of the POST, which apparently the OP doesn't want to happen althought
> it is kind of hard to figure out exactly what he wants. Also, it
> doesn't exit at all. It causes param to return an empty param list,
> and it causes cgi_error to return an error message--no exiting
> involved.

You mean it reads until it detects that the max size has been reached?
Yes, that's what I expect, since one can keep streaming bytes, and only
when the max has been reached the script knows it was too much.

The second part: if the documentation is wrong, it must be fixed. Did you
submit this?

--
John Bokma Freelance software developer
&
Experienced Perl programmer: http://castleamber.com/