Dnia 2015-09-21, pon o godzinie 13:29 -0400, Carl Eberhard pisze:
I'm stumped: * I'm not sure how that url ("http://galaxy.man.poznan.pl/history/view_multipl/api/histories/85b413e771c18...") could have been formed * Calling that link from a local galaxy results in 'No route for' when the error is an api authentication 403 Maybe it's possible that an authentication error is confounding/combining with a client error?
Zuzanna, can you: * tell us what version of Galaxy you're using? * open a javascript console on the history/view_multiple page and see what it says 'galaxy_conf.root' equals?
It took me 13 hours to figure it out but it seems that the problem was caused by this: RequestHeader set X-URL-SCHEME https
inside my <Location />.
I have set it according to the docs: https://wiki.galaxyproject.org/Admin/Config/ApacheProxy as I use apache proxy with SSL, but without it the proxy works fine, as well as uploads and history import. Maybe this case is worth mentioning in the docs.