Expand my Community achievements bar.

SOLVED

Issue accessing folder through URL under 5.6.1

Avatar

Level 3

Just testing an upgrade of one of our CQ 5.4 instances to AEM 5.6.1. One issue we have come across is trying to access a folder through a URL, which used to work under 5.3

We have a program which accesses a folder under the DAM, ie

http://author-server/content/dam

Under 5.6.1 we get an error, ~Forbidden. Cannot serve request to /content/dam/ in org.apache.sling.servlets.get.DefaultGetServlet

The full WebDAV URL will work in 5.6.1,

http://author-server/content/dam/crx/repository/crx.default/content/dam/

Also if we do the following will work

http://author-server/content/dam.json

Is it possible to get 5.6.1 to work as it did under 5.3, so that we don't have to put the full WedDav path in. Otherwise we will need to recode an application which uses the previous functionality

We only need the functionality in Author.

Thank you

1 Accepted Solution

Avatar

Correct answer by
Level 9

Go to Config manager http://localhost:4502/system/console/configMgr

OSGI-> Configuration -> Apache Sling Get Servlet -> Enable HTML (Check on this box)  -> Save

Call this URL http://localhost:4502/content/dam.html

View solution in original post

4 Replies

Avatar

Employee Advisor

Hi,

what kind of result do you expect when you hit "http://author-server/content/dam"?

Kind regards,
Jörg

Avatar

Correct answer by
Level 9

Go to Config manager http://localhost:4502/system/console/configMgr

OSGI-> Configuration -> Apache Sling Get Servlet -> Enable HTML (Check on this box)  -> Save

Call this URL http://localhost:4502/content/dam.html

Avatar

Level 3

Under 5.3 it lists the folder contents, but I believe we just require a successful, 200 response to confirm the folder is there for the program we are running. The full WebDAV URL supplied does give this response, but the short URL doesn't.

Avatar

Level 3

Hmm looks like we might have an issue here, I cant find OSGi --> Configuration in the System Console. I have confirmed it is there for a Vanilla 5.6.1 install, so maybe a possible issue with the upgrade :-(