I'm using hash-based navigation in my rich web app. I also found I needed to create permalinks that would point to single instances of resources, but since I cannot cause the page o refresh, and the main page is loaded from a single path '/', I cannot use real URLs. Instead I thought about using hashes. Let me give you an example because I know the explanation above sucks.

This seems to work ok, and browser believes '#path/to/resource/1' is a hash (slashes permitted, I think) but I was wondering about what characters are allowed in URL hash. Is there a specification or a RFC that I could read to find out what the standard behavior of browsers is when it comes to hashes?

EDIT: Ok, so silly me. Didn't actually check if slashes worked in all browsers. Chrome obviously doesn't like them. Only works in FF.

Didn't actually check if slashes worked in all browsers. Chrome obviously doesn't like them. Only works in FF. - Hmm, I've had no problem in Chrome or any browser for that matter.
–
Wesley MurchMay 3 '11 at 9:20

@Wesley: Dunno, I started using them becuse FF 3.6 agreed it was a good idea. And then I tested in Chrome which behaved differently.
–
bvukelicMay 4 '11 at 10:18

Note: There might be browser inconsistencies. If you fear them, you might use a serialization mechanism, like converting the string to hex or something (will be twice longer though), or use an id of some sort.