Download Flexible authentication for stateless web services

Transcript
void doOptions( HttpServletRequest req, HttpServletResponse res);
void doTrace( HttpServletRequest req, HttpServletResponse res);
The following illustration shows the overall architecture.
Illustration 3: J2EE Container
own creation
The URL of the client request determines which Servlet should to be used. The correct
web application is found in the context root part of the URL.
Example:
http://localhost/geoserver/login.jsp
“geoserver” is the context root and the web application itself knows which servlet is
responsible for /login.jsp.
It is possible to add Java servlet filters between the HTTP client and the servlet. A
filter can modify the request before it is received by the next filter or the servlet at the
end of the chain. The response generated by the servlet may be modified as well when
travelling back to the client.
A filter can also interrupt the chain becoming itself the end point of the request. The
code in the filters and in the servlet is executed within one Java thread. For each http
request a Java thread is created and terminated after the response is sent to the client.
(Most J2EE containers use thread pooling to minimize the effort to create and destroy
23