MicroslingResourceResolver should not go up the path hierarchy for GET requests
-------------------------------------------------------------------------------
Key: SLING-117
URL: https://issues.apache.org/jira/browse/SLING-117
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Bertrand Delacretaz
Priority: Minor
Currently, resolving a request to /content/foo/bar finds the /content/foo
Resource if it exists and if /content/foo/bar doesn't.
This is needed for POST requests that need to create content under non-existing
paths, but for GET this leads to duplicate URLs which point to the same
Resource.
This can be confusing and cause search engines to downgrade site rankings, due
to redundant URLs.
I'll discuss this on list, but I'm creating this issue to make sure we handle
this problem sooner or later.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
