Thanks for the error report. I believe some more recent changes have
been made to address these particular issues:
If these don't address the problem - letting us know the exact path
through the UI to recreate the problem would be of great help in
tracking things down.
On Tue, Dec 2, 2014 at 10:59 AM, Maxime Lévesque
> I have followed the instructions here :
> to run a Galaxy behind an NGinx proxy under with HTTPS,
> The relevant part of my NGinx config has :
> proxy_set_header REMOTE_USER "$loginOnHost";
> proxy_set_header X-Forwarded-Host $host;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_set_header X-URL-SCHEME https;
> it is working well, with the exception that some pages are making external
> to http://genome.ucsc.edu, and not https://genome.ucsc.edu .
> I get a "mixed content" error (in chrome) :
> I verified that the URL that the page is trying to access *does* exist under
> so it's just a matter of telling galaxy to generate HTTPS links. I would
> have thought that
> this is what "proxy_set_header X-URL-SCHEME https;" did...
> https://galaxy-1hge11q-uvd.udes.genap.ca/' was loaded over HTTPS, but
> requested an insecure resource
> This request has been blocked; the content must be served over HTTPS.
> Thanks !
> 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:
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: