Path component disappears

[Rory Douglas]

I have a node at path /sample/content/test, with a child node /entries.  
"entries" has a sling:resourceType="test/EntryList", but there is no 
script registered for that resourceType.

If I browse to http://localhost:8888/sample/content/test/entries       
(i.e no selectors or extension), I get redirected to 
http://localhost:8888/sample/test/entries/

I realize some work has gone on recently with directory listing and 
resource resolution, but is this supposed to happen?

The ResourceResolver mapping property is set to /content/- (a default 
value), which I had interpreted to mean URLs prefixed with /content, not 
all URLs containing /content.  The checkbox next to 
"resource.resolver.new.name" is checked, but like the problem with the 
SlingAuthenticator allow-anonymous-access config, I'm unable to uncheck it.