I've got an upload page that takes in a file, then posts it out to a remote server that listens (using an HttpHandler) for requests, pulls in the file, and saves locally. This all works great, actually, EXCEPT, when the file that is being posted out to the
remote server is > 3 MB. Is there a size limitation to using the WebClient.UploadValues() function? I get a: The remote server returned an error: (400) Bad Request. Error. I think this has something to do with the framework, because it only occurs with larger
sized files. But it could possibly be IIS blocking the POST requests because of the size? Anybody have any ideas about this problem, or possibly a work around?
I actually found a better method to pull in large files by getting in front of IIS and grabbing the raw request stream, parsing it, etc. that way i don't hold the whole file in memory (i chunk it in) and i don't run in to any issue with the maxRequest or requestLength
variable problems (you can only set them so high, eventually you'll time out). Which is exactly what that post was about (could have used it then!) Thanks for your help though.
Member
20 Points
491 Posts
HttpHandler and WebClient class
Mar 06, 2004 02:42 PM|chapel21|LINK
None
0 Points
4 Posts
Re: HttpHandler and WebClient class
Apr 03, 2004 01:35 PM|nonoob|LINK
Member
130 Points
293 Posts
Re: HttpHandler and WebClient class
Apr 03, 2004 08:16 PM|MilanNegovan|LINK
http://www.AspNetResources.com
ASP.NET With Emphasis On Web Standards
Member
20 Points
491 Posts
Re: HttpHandler and WebClient class
Apr 05, 2004 10:54 AM|chapel21|LINK