[
https://issues.apache.org/jira/browse/SLING-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-4671.
---------------------------------
Resolution: Invalid
Looking at your repository it seems you've implemented the required response
handling mechanism in your second commit that handled the 404 component \[1\].
I somehow have the impression that you've created this issue before finishing
the implementation for the error handler, therefore I'd mark this issue as
resolved.
Your proxy configuration doesn't handle Sling 404 properly, btw:
http://slick.millr.org/nothinghere
\[1\] -
https://github.com/auniverseaway/slick/commits/master/src/main/java/net/zum/slick/libs/NotFound.java
> 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)
