[
https://issues.apache.org/jira/browse/SLING-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14937738#comment-14937738
]
Chris Millar commented on SLING-4671:
-------------------------------------
Thanks. A couple notes...
1. Yes, I did see "Reseting the response" in the Sling docs *after* posting
this. In fact, I ended up adding it to the AEM Archetype project:
https://github.com/Adobe-Marketing-Cloud/aem-project-archetype/pull/39
2. I posted this because it seemed like 404.jsp handled different content types
without needing to reset the response. My assumption was that Sightly should
handle it the same way. Maybe I'm wrong on this... I posted this a while ago.
3. Slick is on dispatcher, but wasn't running when you checked, hence
http://slick.millr.org/nothinghere not working. (it now works)
> Sightly does not render correctly when non-HTML resource cannot be found
> ------------------------------------------------------------------------
>
> Key: SLING-4671
> URL: https://issues.apache.org/jira/browse/SLING-4671
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting Sightly Engine 1.0.2
> Environment: Linux / OS X, Sling & Sightly Snapshot.
> Reporter: Chris Millar
> Assignee: Radu Cotescu
> Priority: Minor
> Fix For: Scripting Sightly Engine 1.0.6
>
>
> When creating /apps/sling/servlet/errorhander/404.html
> Sightly template is not rendered correctly for all 404s that are of a
> different resource type.
> The following will result in the sightly template being dumped as plain text:
> http://slick.millr.org/test
> If you browse to a page of the same resource type (html), Sightly renders
> correctly:
> http://slick.millr.org/test.html
> Additionally, images attempt to render, even if they do not exist.
> http://slick.millr.org/test.jpg
> Using JSP, all URLs work as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
