On Thu, Feb 24, 2011 at 4:23 PM, Markus Joschko <[email protected]> wrote: >> Can't you do that using HTTP redirects? >> >> Client requests /permalink/FOO, and a servlet mounted at /permalink >> does an HTTP redirects to the actual resource, using whatever >> mechanism is appropriate based on the semantics of FOO. > > Do redirects also work when doing a POST? We would like to post to > such a URL as well...
If the use case is: -Browser POSTs to the permalink -Sling redirects -Browser should now POST the same thing to new location Then I'm not sure - but I wouldn't a form with a POST email to people anyway, expecting them to execute it much later (as per your original post). > ...Clients are not only browsers but also other systems. We'd like to > keep the handling as simple as possible (therefore the externalid > support)... I think redirects in POST are no problem with non-browser clients, as per http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3 Note that I'm not against expanding the resource resolver - but there might be a simpler and more RESTful way. -Bertrand
