Thanks Simon. Another read on the RFC' and I see that I must have mis-read the first time. I was hoping to use the fragment identifier as a general way of referencing another resource. Looks like I'll have to use the query component.
---------------------------------------- From: Simon Reinhardt <[email protected]> Sent: Sunday, March 15, 2009 11:29 PM To: [email protected] Subject: Re: Handling a URI fragment identifier component using jax-rs? Hi Ty Ty wrote: > Hi, > I can't seem to get a route to work for a URL that has a fragment identifier > component e.g. http://site/page#fragment That's because fragment identifiers don't get sent to the server. Going by the HTTP spec there is no fragment in the request URI so the user agent has to cut it off before making the request and that's what the browsers do. You don't have any chance of getting that information over the request URI. I recommend encoding whatever you want to transfer into the "query" bit. Regards, Simon ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1326645 ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1332160
