Hi,
> >...having the
> > X-Sling-Warning header right next to other headers makes is easy to
> > spot the problem...
On Jan 17, 2008 3:50 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...in this case, we probably
> would rather just not do anything if the
> request.getResponseContentType() i
Hi,
Am Donnerstag, den 17.01.2008, 14:09 +0100 schrieb Bertrand Delacretaz:
> Hi,
>
> I've added this (in revision 612806) to SlingScriptServlet.service(),
> to use an X-Sling-Warning HTTP header to indicate an abnormal
> non-critical condition:
This is certainly of value during development. But
Hi,
I've added this (in revision 612806) to SlingScriptServlet.service(),
to use an X-Sling-Warning HTTP header to indicate an abnormal
non-critical condition:
final String contentType = request.getResponseContentType();
if(contentType == null) {
res.addHeader("X-Sling-Warning",
request.g
