File Post Control

[tajeshwar]

Hi,

I am using file post control to upload a large file to web server. this
file can be very large(5-10 GB).
Now what this control do is that it will reject any such request because
of ASP.NET security features.
Now what I want to do is to handle this thing at HttpModule level. That
is see if the request is for uploading
a file. If so then I should be able to change the content-length
property in headers and make it small so that
the request shouldn't be rejected. Second I should be able to grab the
InputStream and write it into some file store
and keep on rejecting th eread portion from memory. Now in
multipart/form-encoded requests this is not possible.
Because I don't get anything for InputRequestStr eam. I am not able to
find a solution for this problem.

Regards,
Tajeshwar

[Kevin Spencer]

Re: File Post Control

I hate to tell you this, but you are WAY off base. What on earth makes you
think that by changing the content-length property in a header you will make
the file smaller? If I tell you that I'm 25 years old, does that make me any
younger? This ain't magic, you know. It's technology. Looks the same to an
unwashed audience, but actually quite the opposite.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"tajeshwar" <tajeshwars@gra pecity.com> wrote in message
news:##wJvgTpEH A.3728@TK2MSFTN GP09.phx.gbl...[color=blue]
> Hi,
>
> I am using file post control to upload a large file to web server.[/color]
this[color=blue]
> file can be very large(5-10 GB).
> Now what this control do is that it will reject any such request[/color]
because[color=blue]
> of ASP.NET security features.
> Now what I want to do is to handle this thing at HttpModule level.[/color]
That[color=blue]
> is see if the request is for uploading
> a file. If so then I should be able to change the content-length
> property in headers and make it small so that
> the request shouldn't be rejected. Second I should be able to grab the
> InputStream and write it into some file store
> and keep on rejecting th eread portion from memory. Now in
> multipart/form-encoded requests this is not possible.
> Because I don't get anything for InputRequestStr eam. I am not able to
> find a solution for this problem.
>
> Regards,
> Tajeshwar
>
>[/color]

[Kevin Spencer]

Re: File Post Control

Sorry about my over-reaction. It was just shock. Uploading 5-10 GB of data
to a server is NOT something you should do, with VERY few exceptions. Why
don't you put the data on a couple of CDs and FedEx it? It will get there
quicker.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

"tajeshwar" <tajeshwars@gra pecity.com> wrote in message
news:##wJvgTpEH A.3728@TK2MSFTN GP09.phx.gbl...[color=blue]
> Hi,
>
> I am using file post control to upload a large file to web server.[/color]
this[color=blue]
> file can be very large(5-10 GB).
> Now what this control do is that it will reject any such request[/color]
because[color=blue]
> of ASP.NET security features.
> Now what I want to do is to handle this thing at HttpModule level.[/color]
That[color=blue]
> is see if the request is for uploading
> a file. If so then I should be able to change the content-length
> property in headers and make it small so that
> the request shouldn't be rejected. Second I should be able to grab the
> InputStream and write it into some file store
> and keep on rejecting th eread portion from memory. Now in
> multipart/form-encoded requests this is not possible.
> Because I don't get anything for InputRequestStr eam. I am not able to
> find a solution for this problem.
>
> Regards,
> Tajeshwar
>
>[/color]

[Scott Allen]

Re: File Post Control

Hi tajeshwar:

Have you tried changing the maxRequestLengt h attribute of the
<httpRuntime> element in web.config? I don't believe modifying the
headers will circumvent the protection mechanism.

--
Scott

http://www.OdeToCode.com/blogs/scott/

On Tue, 28 Sep 2004 14:20:17 +0530, "tajeshwar"
<tajeshwars@gra pecity.com> wrote:
[color=blue]
>Hi,
>
> I am using file post control to upload a large file to web server. this
>file can be very large(5-10 GB).
> Now what this control do is that it will reject any such request because
>of ASP.NET security features.
> Now what I want to do is to handle this thing at HttpModule level. That
>is see if the request is for uploading
> a file. If so then I should be able to change the content-length
>property in headers and make it small so that
> the request shouldn't be rejected. Second I should be able to grab the
>InputStream and write it into some file store
> and keep on rejecting th eread portion from memory. Now in
>multipart/form-encoded requests this is not possible.
> Because I don't get anything for InputRequestStr eam. I am not able to
>find a solution for this problem.
>
>Regards,
>Tajeshwar
>[/color]

[Patrice]

Re: File Post Control

Also are those files uploaded by end users ???!!! If not I would consider to
change the arhcitecture if posisble. You could also transfer changes instead
of uploaidng the whole thing each time (or is this already just the changes
!!!).

Patrice

--

"tajeshwar" <tajeshwars@gra pecity.com> a écrit dans le message de
news:%23%23wJvg TpEHA.3728@TK2M SFTNGP09.phx.gb l...[color=blue]
> Hi,
>
> I am using file post control to upload a large file to web server.[/color]
this[color=blue]
> file can be very large(5-10 GB).
> Now what this control do is that it will reject any such request[/color]
because[color=blue]
> of ASP.NET security features.
> Now what I want to do is to handle this thing at HttpModule level.[/color]
That[color=blue]
> is see if the request is for uploading
> a file. If so then I should be able to change the content-length
> property in headers and make it small so that
> the request shouldn't be rejected. Second I should be able to grab the
> InputStream and write it into some file store
> and keep on rejecting th eread portion from memory. Now in
> multipart/form-encoded requests this is not possible.
> Because I don't get anything for InputRequestStr eam. I am not able to
> find a solution for this problem.
>
> Regards,
> Tajeshwar
>
>[/color]

[Scott Allen]

Re: File Post Control

Oops, I read 5-10 MB when I first read the post and wondered what all
the excitement was about. 10GB is a bit much for HTTP...

--
Scott

http://www.OdeToCode.com/blogs/scott/

On Tue, 28 Sep 2004 08:55:30 -0400, "Kevin Spencer"
<kspencer@takem pis.com> wrote:
[color=blue]
>Sorry about my over-reaction. It was just shock. Uploading 5-10 GB of data
>to a server is NOT something you should do, with VERY few exceptions. Why
>don't you put the data on a couple of CDs and FedEx it? It will get there
>quicker.[/color]

[Ken Cox [Microsoft MVP]]

RE: File Post Control

I suspect you're going to need a heavy duty, resumable upload component for
that. Try here?

http://fileup.softartisans.com/fileup-147.aspx

"tajeshwar" wrote:
[color=blue]
> Hi,
>
> I am using file post control to upload a large file to web server. this
> file can be very large(5-10 GB).
> Now what this control do is that it will reject any such request because
> of ASP.NET security features.
> Now what I want to do is to handle this thing at HttpModule level. That
> is see if the request is for uploading
> a file. If so then I should be able to change the content-length
> property in headers and make it small so that
> the request shouldn't be rejected. Second I should be able to grab the
> InputStream and write it into some file store
> and keep on rejecting th eread portion from memory. Now in
> multipart/form-encoded requests this is not possible.
> Because I don't get anything for InputRequestStr eam. I am not able to
> find a solution for this problem.
>
> Regards,
> Tajeshwar
>
>
>[/color]