GW> If you are using a filter, why not wrap the response
GW> object and implement sendError yourself.
cool! I'll try. Thanks again!
alex
GW> cheers
GW> Alex Loubyansky wrote:> Thank you very much, Greg.
>>
>> I am hacking OSCache filter that caches content. The problem is not to
>> cache er
Thank you very much, Greg.
I am hacking OSCache filter that caches content. The problem is not to
cache error pages.
I tried to check request attributes and
javax.servlet.error.servlet_name is really set to 'action' and I could
make use of it. But as I got you right, it's not the right way.
Do s
ease see http://jetty.mortbay.org
>>
>> To alter your subscription to this list goto
>http://groups.yahoo.com/group/jetty-discuss
>>
>> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>>
>>
>>
>>
forwarding you to Jetty-Discuss...
Jules
--- Begin Message ---
Should javax.servlet.error.status_code attribute contain a
corresponding value in case of HTTP error?
Is it mandatory by the spec?
With Jetty that comes with current JBoss-3.2.0beta2 status_code is
null for 404 (haven't tried othe
>From servlet-2_3-fcs-spec.pdf:
SRV.9.9.1 Request Attributes
...If the location of the error handler is a servlet or a JSP page, the request
attributes in Table SRV.9-1 must be set.
javax.servlet.error.status_code java.lang.Integer
javax.servlet.error.exception_type java.lang.Class
javax.serv
Should javax.servlet.error.status_code attribute contain a
corresponding value in case of HTTP error?
Is it mandatory by the spec?
With Jetty that comes with current JBoss-3.2.0beta2 status_code is
null for 404 (haven't tried others).
But servlet_name has a value set in case of error.
The attribu
