Re: Upload a very large file to a DirectAction
Re: Upload a very large file to a DirectAction
- Subject: Re: Upload a very large file to a DirectAction
- From: Mike Schrag <email@hidden>
- Date: Wed, 22 Oct 2008 07:54:21 -0400
<com.webobjects.appserver._private.WOHttpIO> Unable to parse content-
length header: '2472285238'.
<com.webobjects.appserver._private.WOHttpIO> Unable to parse content-
length header: '2472285238'.
WOHttpIO parses the content length header as an int, which gives you a
maximum value of 2.1G. Oddly, 5.4 changed the response code to take a
long, but it looks like this was overlooked.
Is there a solution/workaround for this?
The only workaround is either remove the content-length header (if you
control the client), which MIIIGGHT work -- I'm just glancing at the
code here, but it does go through a different path if the header is
missing, or you're going to have to jad and replace WOHTTPIO and
WOInputStreamData.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden