-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
> Arg.. this is really gonna bug me.. cause I have seen that behavior from
> Jserv before... uhh... how's your classpath lookin? (that seems to be a
> stock answer). try /usr/local/apache/logs/jserv.log..
Okay, well, here are some more details to whet your appetite for
bugs. This is the servlet which responds to my "multipart/form-data"
file upload, if you recall, and the directory that it wants to save
the uploads in is not writable.
Well, if I submit bogus filenames for the upload, then the servlet,
upon discovering that the directory it was going to save the files to
is not writable, does the right thing and reports the unexpected
problem to the user. But if I submit real files, then it gives me an
empty response.
So maybe in the first case, the request doesn't include the files'
contents (since the files don't exist), whereas the second one does.
And then the fact that (upon discovering that the save directory is
invalid) the servlet doesn't parse the request somehow makes it unable
to return any output?
(I'm frustrated that I'm spending so much time tracking down a bug
that will "never happen"... I really don't expect to have problems
writing to the directory, but I felt I should prepare for this
eventuality anyway.)
Hmm... why is it that the print() and println() methods of PrintWriter
can't throw IOError, but the write() methods can? Maybe there's an
error on the stream but the servlet is blithely printing more data
cause no exception is thrown. I'll look into this more.
Solomon
--
Solomon <|> [EMAIL PROTECTED]
Douglas /|\ http://web.mit.edu/srcd/www/
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
