O'Reilly upload servlet issues

Adrian Hill

unread,

Apr 23, 2001, 8:25:24 AM4/23/01

to

Hi there,

I have been using the com.oreilly.servlet.MultipartRequest object
http://www.servlets.com/cos/ ) to upload files using a form fill-in. This
object has worked really nicely, until I uploaded the pages that use it onto
another server (exactly the same permissions, versions etc. as the last
server). I had two different sections which used it, and although one
section works nicely still, the other one keeps calling the following
exception when the MultipartRequest object is instantiated (where the files
are uploaded):

Error: 500
Location: /admin/recommendation_admin3.jsp
Internal Servlet Error:

java.io.IOException: Corrupt form data: no leading boundary
at
com.oreilly.servlet.MultipartRequest.readRequest(MultipartRequest.java:280)
at com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:140)
at com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:96)

I am using: tomcat v3.2.1 with mod_jserve and apache v3.1.12

Has anyone got any suggestions? Any help would be much appreciated.
Regards,

Adrian Hill

Russell Gold

unread,

Apr 24, 2001, 11:14:59 PM4/24/01

to

In article <te87q15...@corp.supernews.co.uk>, "Adrian Hill"
<nospam...@thank.you.com> wrote:

There is a bug in the oreilly classes. When the boundary tag used is very
long, it can wrap to a separate header line; unfortunately, the oreilly
classes do not handle this. This has been reported to Jason Hunter; I
presume that he will release an updated version at some point.

The reason that you are seeing different behavior is probably that the
creation of the boundary strings is often VM-dependant.

--
russ...@acm.org http://www.httpunit.org

Cowboy Bob

unread,

Apr 25, 2001, 7:30:20 AM4/25/01

to

There are many bugs in O'Reilly. On one project I had orignally been specified
to build on O'Reilly, which I did. Bu there were *awful* problems with
authentication, session tracking and many "lost" sessions. I ported to Tomcat
and it works like a dream....

Bob

On Tue, 24 Apr 2001 23:14:59 -0400, in post
<russgold-240...@dsl-64-194-231-17.telocity.com>, Russell Gold opend
their fat mouth and spewed forth:

"All I wanted in the end was world domination and a whole lot of money to spend"
- Justin Sullivan

Simon Brooke

unread,

Apr 26, 2001, 2:58:43 PM4/26/01

to

on Wednesday 25 April 2001 04:14, Russell Gold wrote:

> In article <te87q15...@corp.supernews.co.uk>, "Adrian Hill"
> <nospam...@thank.you.com> wrote:
>
>> Hi there,
>>
>> I have been using the com.oreilly.servlet.MultipartRequest object
>> http://www.servlets.com/cos/ ) to upload files using a form fill-in.

<snip>

>>
>> java.io.IOException: Corrupt form data: no leading boundary
>> at
>>
com.oreilly.servlet.MultipartRequest.readRequest(MultipartRequest.java:280)
>> at com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:140)
>> at com.oreilly.servlet.MultipartRequest.(MultipartRequest.java:96)
>>
>> I am using: tomcat v3.2.1 with mod_jserve and apache v3.1.12
>>
>> Has anyone got any suggestions? Any help would be much appreciated.
>> Regards,
>
> There is a bug in the oreilly classes. When the boundary tag used is
> very long, it can wrap to a separate header line; unfortunately, the
> oreilly classes do not handle this. This has been reported to Jason
> Hunter; I presume that he will release an updated version at some
> point.

Could you post (or mail me) instructions which would allow me to
reproduce this bug? I'm fairly sure my own maybeupload library would
fall over in exactly the same way, and I'd like to fix it if I can.

> The reason that you are seeing different behavior is probably that the
> creation of the boundary strings is often VM-dependant.

The boundary strings aren't created server-side, they're created
client-side... so changing the server shouldn't change them, surely?

--
si...@jasmine.org.uk (Simon Brooke) http://www.jasmine.org.uk/~simon/

;; Madness takes its toll. Please have exact change.