> >I have no clue what is servlet doing - you've the stack trace.
> > It's not the servlet the web server who's throwning the exception,
> >
>
> There is a bug in jsdk's readLine() method (it was ignoring len):
Yes, but that bug causes an ArrayIndexOOBE on super-long lines, not an
IOException. This bug is something else, unfortunately something we'll
not really be able to determine from here. All we know is the
Content-Disposition header is corrupted since "w?" isn't a valid value.
Why's it corrupted? Well, I'd test with other servlet engines. I'd
try snooping the client's request looking for perhaps a corrupted
header. Bina, time to put on your debugging hat.
-jh-
--
Jason Hunter
[EMAIL PROTECTED]
Book: http://www.servlets.com/book
2.0 to 2.1: http://www.javaworld.com/jw-12-1998/jw-12-servletapi.html
2.1 to 2.2: http://www.javaworld.com/jw-10-1999/jw-10-servletapi.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
