Hi everyone,
I found some inconsistency between URL processing in sling.include and a
URL processed in an HTTP GET request.
If I do an HTTP request for the following:
/content/resource./mysuffix.html
The request is processed as:
resourcePath: /content/resource
extension: null
selectors: null
suffix: /mysuffix.html
Whereas if I do:
sling.include(/content/resource./mysuffix.html), what I get is:
resourcePath: /content/resource/mysuffix
extension: html
selectors: null
suffix: null
Judging solely by the assertions in the RPI unit test [1], the HTTP
request URL decomposition is correct, and the sling.include handler has
a bug. Unless a sling include is *not* supposed to be synonymous with a
GET request?
Best,
Branden
[1]
http://svn.apache.org/repos/asf/sling/trunk/bundles/engine/src/test/java/org/apache/sling/engine/impl/request/SlingRequestPathInfoTest.java
