Hi, I think recursively going up the path in the MicroslingResourceResolver can lead to confusion and redundant GET URLs.
Do we really need suffixes? I'm still a bit confused about their goals for GET requests. Maybe we could simplify the Resource resolution, here's a suggested example where only /content/foo exists: /content/foo -> HTTP status code 200 /content/foo.html -> 200, extension=html /content/foo.print.a4.html -> 200, extension=html, selectors=print.a4 /content/foo/bar -> 404 /content/foo.html/bar -> 404 This would be for GET/HEAD requests only, as POSTs need the extra path components. Basically, the only separators allowed after the path of an existing resource would be dots. Of course, if someone has a real use case for suffixes in GET requests I'm open to that, but right now I don't see what suffixes bring that cannot be done with selectors. WDYT? -Bertrand
