You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Rohit Nijhawan (Commented) (JIRA)" <ji...@apache.org> on 2012/01/27 23:22:11 UTC

[jira] [Commented] (SLING-2179) 403 instead of 404 response after stopping bundle

    [ https://issues.apache.org/jira/browse/SLING-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195152#comment-13195152 ] 

Rohit Nijhawan commented on SLING-2179:
---------------------------------------

I second that. Sling is not easy to get right the first time especially if you're hooking it up to a database like oracle. I can upload and download with full URL paths but i can't browse the tree (content node isn't there) and i had to fight off a lot of repository lock issues.

A resolution would be nice.
                
> 403 instead of 404 response after stopping bundle
> -------------------------------------------------
>
>                 Key: SLING-2179
>                 URL: https://issues.apache.org/jira/browse/SLING-2179
>             Project: Sling
>          Issue Type: Bug
>          Components: Servlets
>            Reporter: Reto Bachmann-Gmür
>            Priority: Minor
>
> - Before starting "Apache Sling Launchpad Testing Services" (compiled from launchpad/test-services" on http://localhost:8080/testing/PathsServlet/foo/ I correctly get a 404 response
> - After starting the bundle I correctly get a 200 response
> - After stopping the bundle I get a 403 response
> - After restarting the OSGI container the expected 404 response is returned again
> Body of the unexpected 403 response:
> <h1>Forbidden (403)</h1>
> <p>The requested URL /testing/PathsServlet/foo/ resulted in an error in org.apache.sling.servlets.get.DefaultGetServlet.</p>
> <h3>Request Progress:</h3>
> <pre>
>       0 (2011-08-15 11:54:45) TIMER_START{Request Processing}
>       0 (2011-08-15 11:54:45) COMMENT timer_end format is {&lt;elapsed msec&gt;,&lt;timer name&gt;} &lt;optional message&gt;
>       0 (2011-08-15 11:54:45) LOG Method=GET, PathInfo=/testing/PathsServlet/foo/
>       0 (2011-08-15 11:54:45) TIMER_START{ResourceResolution}
>       0 (2011-08-15 11:54:45) TIMER_END{0,ResourceResolution} URI=/testing/PathsServlet/foo/ resolves to Resource=SyntheticResource, type=sling:syntheticResourceProviderResource, path=/testing/PathsServlet/foo
>       0 (2011-08-15 11:54:45) LOG Resource Path Info: SlingRequestPathInfo: path='/testing/PathsServlet/foo', selectorString='null', extension='null', suffix='/'
>       0 (2011-08-15 11:54:45) TIMER_START{ServletResolution}
>       0 (2011-08-15 11:54:45) TIMER_START{resolveServlet(SyntheticResource, type=sling:syntheticResourceProviderResource, path=/testing/PathsServlet/foo)}
>       0 (2011-08-15 11:54:45) TIMER_END{0,resolveServlet(SyntheticResource, type=sling:syntheticResourceProviderResource, path=/testing/PathsServlet/foo)} Using servlet org.apache.sling.servlets.get.DefaultGetServlet
>       0 (2011-08-15 11:54:45) TIMER_END{0,ServletResolution} URI=/testing/PathsServlet/foo/ handled by Servlet=org.apache.sling.servlets.get.DefaultGetServlet
>       0 (2011-08-15 11:54:45) LOG Applying Requestfilters
>       0 (2011-08-15 11:54:45) LOG Calling filter: org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
>       0 (2011-08-15 11:54:45) TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
>       0 (2011-08-15 11:54:45) LOG Using org.apache.sling.servlets.get.impl.helpers.StreamRendererServlet to render for extension=null
>       1 (2011-08-15 11:54:45) TIMER_START{handleError:status=403}
>       2 (2011-08-15 11:54:45) TIMER_END{1,handleError:status=403} Using handler org.apache.sling.servlets.resolver.internal.defaults.DefaultErrorHandlerServlet
>       2 (2011-08-15 11:54:45) TIMER_END{2,Request Processing} Dumping SlingRequestProgressTracker Entries
> </pre>
> <hr>
> <address>ApacheSling/2.2 (Java HotSpot(TM) Server VM 1.6.0_26; Linux 2.6.38-10-generic-pae i386)</address>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira