Thanks Jonas, exactly what I was looking for!

Jörn

On Fri, Feb 6, 2009 at 4:20 PM, Jonas <[email protected]> wrote:
> Hi,
>
> this isn't actually related to wicket, but anyway, I think what you're
> looking for is
> the servlet request attribute "javax.servlet.error.request_uri"
> See: http://www.servlets.com/soapbox/servlet23.html
> specially the section 'New error attributes'
>
> regards,
> Jonas
>
>
> On Fri, Feb 6, 2009 at 3:28 PM, Jörn Zaefferer
> <[email protected]> wrote:
>> Hi,
>>
>> I'm using a servlet error-page mapping to display my custom NotFound
>> page for 404s (eg. as described here:
>> http://herebebeasties.com/2006-12-20/using-a-servlet-filter-for-404-error-page/)
>>
>> <filter-mapping>
>>        <filter-name>wicket-filter</filter-name>
>>        <url-pattern>/*</url-pattern>
>>        <dispatcher>REQUEST</dispatcher>
>>        <dispatcher>ERROR</dispatcher>
>> </filter-mapping>
>>
>> <error-page>
>>        <error-code>404</error-code>
>>        <location>/404</location>
>> </error-page>
>>
>> I have some anlayzing code on my NotFound page to check where the 404
>> occured, eg. by looking at the referrer and logging the request URI.
>> This works when I use setResponsePage(NotFound.class) in other pages,
>> but not for the error-page mapping, as
>> HttpServletRequest#getRequestURI() returns just /404, which isn't
>> helping at all.
>>
>> Any ideas on how to get at the original URI that triggered the 404?
>>
>> Jörn
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to