Hello Daniel,
you should "mount" (I prefer associate, but that's just me ;)) your
resource, or preferably, another one, at /proxy/{some_resource_id} to
be able to access resources at /proxy/resource_id_1,
/proxy/resource_id_2, etc.
This is because indeed /proxy/ and /proxy/anything are different
matches. The slash is special in the sense that it's the URI path
separator, I guess that's why by default the routing logic is so
"picky" about it.
Hope this helps.
On Mon, May 7, 2012 at 5:36 AM, Daniele Dellafiore <[email protected]> wrote:
> Hi everyone.
>
> I'm mounting resources like this:
>
> /proxy/
>
> and it actually matter if I use the final slash or not. In fact, with
> that declaration, the app does answer a 404 on /proxy without the
> final slash. That's fine.
> But if I use that same declaration and I do call
>
> /proxy/anything
>
> I still get a 404.
> I can I make the very same resource java file to get all the /proxy/* calls?
>
> Thanks.
>
> --
> Daniele Dellafiore
> http://danieledellafiore.net
>
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2958188
--
Fabián Mandelbaum
IS Engineer
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2958251
