Glad you figured it out!  So a page served via https is generating links for http references that should have been https?

On Mon, Sep 21, 2015 at 5:15 PM, Zuzanna K. Filutowska <> wrote:
Dnia 2015-09-21, pon o godzinie 13:29 -0400, Carl Eberhard pisze:
> I'm stumped:
>       * I'm not sure how that url
>         ("") 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:
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.



Zuzanna K. Filutowska, HPC Systems Administrator
Poznan Supercomputing and Networking Center
Institute of Bioorganic Chemistry Polish Academy of Sciences
Seize the day boys! Make your lifes extraordinary! --John Keating

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:

To search Galaxy mailing lists use the unified search at: