Hi,
See SLING-207, in an ESP script like this one:
body
%
sling.include(resource.getPath() + .html);
%
/body
The include rightly causes a server error due to the (just added)
SLING-208 infinite loop detection.
However, client receives a status 200 OK in this case. Do we want
Hi,
Am Dienstag, den 29.01.2008, 08:41 +0100 schrieb Bertrand Delacretaz:
On Jan 29, 2008 8:28 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...If the response has already been committed at the time the infinte loop
detection aborts processing, it is not possible to send 500 any more
Hi,
I agree, that returning 500 might be desirable, but
If the response has already been committed at the time the infinte loop
detection aborts processing, it is not possible to send 500 any more.
There is also a difference in request inclusion between Sling and the
Servlet API: In the
