Hi James, James Taylor wrote, On 02/02/2010 07:27 PM:
1. It is still possible to share histories without having a public name. ( maybe rev 3255:ea652508497a doesn't catch all possible cases ? ) the shared history gets a URL of "http://localhost:8080/u//h/unnamed-history" (which gives a "404 not found").
No, a history has to have a public name to be shared. However I'm not sure that is the problem in this case. This history has the name "unnamed-history". Have you enabled import for this history?
The history had a name, it's my registered user which didn't have a public name (in the URL, the part between the /u/ and the /h/ is empty).
I think we can address these issues. You are right however that it *is* now possible for a user to change the url to a history. This is deliberate. There are a number of problems with the ID hashing approach we were using, primarily that ID stability relies of a secret key.
I actually liked the hashed-id very much... it was stable and reproducible, and supposedly safe (assuming the galaxy admin replaced the "changethisinproductiontoo" in the INI file). You're still going to use hashed-id for public datasets and workflows, aren't you? Thanks for your reply, -gordon