On Mon, Mar 31, 2008 at 3:54 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> > OK - how about introducing a new filter.scope - e.g. "prerequest", and > > alter SlingMainServlet so that it invokes "prerequest" filters before > > passing the request to the ResourceResolver? > > Sounds interesting. Such a filter would be defined to get the original > request and response objects from the servlet container. That is they > would be HttpServletRequest/Response and not > SlingHttpServletRequest/Response. > > Would that suit your needs ? Ah ... but this would be a catch 22, wouldn't it, as the sling.include scenario will still be a problem: > So that a request from a browser to http://www.domain.com/path would > yield a different result than sling.include("/path"). Or am I missing something here? -- Vidar S. Ramdal <[EMAIL PROTECTED]> - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway
