-----------------------------
Please read the FAQ!
<http://java.apache.org/faq/>
-----------------------------
I wrote:
> What sort of circumstances could cause my browser to keep spinning
> even after the servlet has called out.close()? The browser (Netscape)
> has received all the data, and yet I have to hit "stop" (at which
> point it says "transfer interrupted").
Michael Amster <[EMAIL PROTECTED]> responded:
> Are you sending out a content-length that does not match the amount of
> data sent? Have you tested it with a connection via telnet? Have you
> flushed the writer prior to close?
I'm not setting the content length. This is what I'm doing, which is
just about the same as I do for most of my other servlets, which don't
suffer from this problem:
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.print(... a bunch of times ...);
out.flush(); // whether or not i include this line has no effect
out.close();
When I try it with telnet, I see that there is no Content-Length
header at all. Is that bad?
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]
