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

Reply via email to