|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectorg.mortbay.servlet.RestFilter
public class RestFilter
Support for HTTP PUT and DELETE methods.
THIS FILTER SHOULD ONLY BE USED WITH VERY GOOD SECURITY CONSTRAINTS!
If the filter init parameter maxPutSize is set to a positive integer, then only puts of known size less than maxPutSize will be accepted.
Constructor Summary | |
---|---|
RestFilter()
|
Method Summary | |
---|---|
void |
destroy()
Called by the web container to indicate to a filter that it is being taken out of service. |
protected void |
doDelete(HttpServletRequest request,
HttpServletResponse response)
|
void |
doFilter(ServletRequest request,
ServletResponse response,
FilterChain chain)
The doFilter method of the Filter is called by the container
each time a request/response pair is passed through the chain due
to a client request for a resource at the end of the chain. |
protected void |
doPut(HttpServletRequest request,
HttpServletResponse response)
|
void |
init(FilterConfig filterConfig)
Called by the web container to indicate to a filter that it is being placed into service. |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
---|
public RestFilter()
Method Detail |
---|
public void init(FilterConfig filterConfig) throws UnavailableException
Filter
init
in interface Filter
UnavailableException
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws java.io.IOException, ServletException
Filter
doFilter
method of the Filter is called by the container
each time a request/response pair is passed through the chain due
to a client request for a resource at the end of the chain. The FilterChain passed in to this
method allows the Filter to pass on the request and response to the next entity in the
chain.
A typical implementation of this method would follow the following pattern:-
1. Examine the request
2. Optionally wrap the request object with a custom implementation to
filter content or headers for input filtering
3. Optionally wrap the response object with a custom implementation to
filter content or headers for output filtering
4. a) Either invoke the next entity in the chain using the FilterChain object (chain.doFilter()
),
4. b) or not pass on the request/response pair to the next entity in the filter chain to block the request processing
5. Directly set headers on the response after invocation of the next entity in the filter chain.
doFilter
in interface Filter
java.io.IOException
ServletException
protected void doPut(HttpServletRequest request, HttpServletResponse response) throws ServletException, java.io.IOException
request
- response
-
ServletException
java.io.IOException
protected void doDelete(HttpServletRequest request, HttpServletResponse response) throws ServletException, java.io.IOException
request
- response
-
ServletException
java.io.IOException
public void destroy()
Filter
destroy
in interface Filter
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |