On 09/04/2015 19:50, George Sexton wrote: > Chris > > On 4/9/2015 10:06 AM, Christopher Schultz wrote: >> Just my two cents, but any server that works the way you want is >> not compliant with the servlet specification. It states that all >> requests for a context must be passed to the container. >> ?? >> >> The servlet spec doesn't apply to environments, only containers. If >> the OP wants to have Apache httpd serve static files and proxy dynamic >> requests, that's perfectly reasonable. > > Quoting Servlet Specification 3.0, section 4.1 Servlet context, it says: > > /A ServletContext is rooted at a known path within a Web server. For > example, a servlet context could be located at > http://www.mycorp.com/catalog. All requests that begin with the /catalog > request path, known as the context path, are routed to the Web > application associated with the ServletContext.// > / > My reading of it says that any request that matches a known context path > must be routed to the web application. It seems pretty cut and dried to me. > > Can you help me understand why that's not the case?
It only applies to requests that reach the WebContainer (in this case Tomcat). What happens before that in terms of reverse proxies is out of scope for the Servlet spec. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
