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 Servlet API it is not allowed for included requests to set headers (I understand this such that included requests are also not able to set the response status code), while in Sling this restriction does not exist. Regards Felix Am Montag, den 28.01.2008, 15:38 +0100 schrieb Bertrand Delacretaz: > 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 that? > > For some status codes, say if the included request causes a 404, it > might make sense to still return 200 for the page request, but I think > a 500 should be relayed to the client. > > -Bertrand
