[
https://issues.apache.org/jira/browse/SLING-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762175#action_12762175
]
Peter Chiochetti commented on SLING-1134:
-----------------------------------------
A wish: please make sling behave in that case like specified in this document:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4 - i.e. send a
401 Unauthorized.
As browsers cache the credentials, a result code of 200 will not trigger a new
authentication, which is especially useful, if eg. a user mistyped name or
password - she then should get a chance to correct the error. Doing XHR
requests instead is a little fragile too.
> GET for http://localhost:8080/ results in HTTP ERROR 200
> --------------------------------------------------------
>
> Key: SLING-1134
> URL: https://issues.apache.org/jira/browse/SLING-1134
> Project: Sling
> Issue Type: Bug
> Components: Launchpad
> Affects Versions: Launchpad App 6
> Environment: Mac OS X 10.6.1, java version "1.6.0_15"
> Firefox (3.5.3)
> Reporter: Andreas Amstutz
> Attachments: error.log, sling.diff
>
>
> A GET for http://localhost:8080/ results in HTTP ERROR 200
> Steps to reproduce this:
> 1) svn checkout http://svn.apache.org/repos/asf/sling/trunk Sling
> 2) mvn -s /dev/null install (I had to apply the attached
> sling.diff for this to be successful)
> 3) cd launchpad/app/
> 4) java -jar target/org.apache.sling.launchpad.app-6-SNAPSHOT.jar -c sling
> 5) http://localhost:8080/system/console
> 6) set "Allow Anonymous Access" to false
> (org.apache.sling.engine.impl.auth.SlingAuthenticator)
> 7) go to http://localhost:8080/
> Result:
> - The log says: org.apache.sling.engine.impl.auth.SlingAuthenticator
> getAnonymousSession: Anonymous access not allowed by configuration -
> redirecting to login
> - Firefox: HTTP ERROR 200 , Problem accessing /. Reason: OK
> There is also quite a lot of noise in the error.log:
> *WARN* [SCR Component Actor]
> org.apache.sling.jcr.jackrabbit.server.impl.security.PluggableDefaultAccessManager
> No pluggable AccessManager available, falling back to DefaultAccessManager
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
