Hi, Daniel, The configuration suggested at http://wiki.g2.bx.psu.edu/Admin/Config/Apache%20Proxy is what you followed to set your proxy up?
That obfuscated link hash element is generated from internal database ids to help secure against malicious users viewing specific datasets - not something your web server configuration normally needs to know about or do anything about. The Galaxy paste process takes care of generating and interpreting them. If you want to dig deeper, the external scripting api has code for accessing datasets by generating the right hashes - see code and minimal docs at scripts/api On Fri, Jun 8, 2012 at 7:59 AM, Dorset, Daniel C <[email protected]> wrote: > I appreciate you taking the time to help! I'm almost positive it's a local > configuration issue, like you said, but without knowing how Galaxy generates > or parses its internal links (in the form of [Galaxy web > address]/datasets/[16 character hash]/display/[filename] ) it's tough to know > how to attack the problem. I dug through some of the database tables in psql, > but I couldn't find much of interest there either. > > hg tip result is: 7148:17d57db9a7c0 <-- that's the May 9th release > > Thanks again for your help! > > Dan > -- Ross Lazarus MBBS MPH; Associate Professor, Harvard Medical School; Head, Medical Bioinformatics, BakerIDI; Tel: +61 385321444; ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
