File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Component Certification (SCWCD/OCPJWCD) and the fly likes Why status code is not buffered? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Web Component Certification (SCWCD/OCPJWCD)
Bookmark "Why status code is not buffered?" Watch "Why status code is not buffered?" New topic

Why status code is not buffered?

Guennadiy VANIN
Ranch Hand

Joined: Aug 30, 2001
Posts: 898
Beginner question:
Originally posted in
[url = ] Professional SCWCD Sample Chapter, p.88-89
"The first line of the server response contains the status code (200 in this case), followed by any headers, finally the border of the response.
Therefore, if the response has already been committed (or flushed) it is too late to change the status: it will have already been sent before the response body has just been committed.
HTTP headers do not cause a problem as they are buffered by the servlet and returned all at once. Therefore, the status may be set after a header has been set.

I would like to ask in this connection:
What are potential problems sending the wrong or null status code?
Why status code is not buffered?
Suppose, that HTTP headers are not buffered and what problem would it create?
Does it mean that status is always sent with headers and border, while headers are constantly monitored and may be sent separately on change?
[ December 17, 2002: Message edited by: G Vanin ]
I agree. Here's the link:
subject: Why status code is not buffered?
It's not a secret anymore!