com.arsdigita.acs.bboard
Class DownloadFile
java.lang.Object
|
+--javax.servlet.GenericServlet
|
+--javax.servlet.http.HttpServlet
|
+--com.arsdigita.acs.bboard.DownloadFile
- All Implemented Interfaces:
- Serializable, Servlet, ServletConfig
- public class DownloadFile
- extends HttpServlet
Serves as a registered procedure for path
/bboard/download-file//pretty-name.
- See Also:
- Serialized Form
Methods inherited from class javax.servlet.GenericServlet |
destroy, getInitParameter, getInitParameterNames, getServletConfig, getServletContext, getServletInfo, getServletName, init, init, log, log |
Methods inherited from class java.lang.Object |
, clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
DownloadFile
public DownloadFile()
doGet
public void doGet(HttpServletRequest req,
HttpServletResponse resp)
throws ServletException
- Description copied from class:
HttpServlet
- Called by the server (via the
service
method) to
allow a servlet to handle a GET request.
Overriding this method to support a GET request also
automatically supports an HTTP HEAD request. A HEAD
request is a GET request that returns no body in the
response, only the request header fields.
When overriding this method, read the request data,
write the response headers, get the response's writer or
output stream object, and finally, write the response data.
It's best to include content type and encoding. When using
a PrintWriter
object to return the response,
set the content type before accessing the
PrintWriter
object.
The servlet container must write the headers before
committing the response, because in HTTP the headers must be sent
before the response body.
Where possible, set the Content-Length header (with the
ServletResponse.setContentLength(int)
method),
to allow the servlet container to use a persistent connection
to return its response to the client, improving performance.
The content length is automatically set if the entire response fits
inside the response buffer.
The GET method should be safe, that is, without
any side effects for which users are held responsible.
For example, most form queries have no side effects.
If a client request is intended to change stored data,
the request should use some other HTTP method.
The GET method should also be idempotent, meaning
that it can be safely repeated. Sometimes making a
method safe also makes it idempotent. For example,
repeating queries is both safe and idempotent, but
buying a product online or modifying data is neither
safe nor idempotent.
If the request is incorrectly formatted, doGet
returns an HTTP "Bad Request" message.
- Overrides:
doGet
in class HttpServlet
- Following copied from class:
javax.servlet.http.HttpServlet
- Parameters:
req
- an HttpServletRequest
object that
contains the request the client has made
of the servletresp
- an HttpServletResponse
object that
contains the response the servlet sends
to the client- Throws:
IOException
- if an input or output error is
detected when the servlet handles
the GET requestServletException
- if the request for the GET
could not be handled- See Also:
ServletResponse.setContentType(java.lang.String)