On Tue, Nov 19, 2013 at 12:32 PM, Jingchao Zhang <zh...@unl.edu> wrote:
> Hi Peter,
> Thanks so much for your help! It is like you said a browser issue.
> I also noticed that the Galaxy main server (https://usegalaxy.org/)
> doesn't have this problem. And their USCS main table browser uses "https"
> instead of "http". Does anyone know why this isn't included in the current
> Galaxy release? And how can I change my current "http USCS main" to "https
> USCS main"?
We did this for usegalaxy.org simply by locally changing the URL in the
tool's config from http to https. A proper fix for this tool (and other
external sites which open in the center iframe) is in the works and will be
released to the stable branch once it's done.
> Message: 8
> Date: Tue, 19 Nov 2013 08:51:03 +0000
> From: Peter Briggs <peter.bri...@manchester.ac.uk>
> To: firstname.lastname@example.org
> Subject: Re: [galaxy-dev] secure Galaxy with SSL
> Message-ID: <528b2677.9050...@manchester.ac.uk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Hello Jim
> Re your problem #1 (UCSC browser appears to be blocked), I've seen
> something similar with our local Galaxy instance, which is also served
> via https.
> In our case I believe this is actually a browser issue: the latest
> version of Firefox silently blocks mixed secure and insecure content:
> (I think Chrome and IE do something similar, although IE at least gives
> a warning.)
> The workaround is either to disable mixed content blocking (not trivial
> in Firefox, and probably not a good idea in general), or to do something
> like e.g. right-click "Open link in new tab" on the "Get data"/"UCSC
> main table browser" link in Galaxy.
> Once UCSC has loaded in the new tab it can be used to send data back to
> Galaxy without any problems.
> Best wishes, Peter
> On 18/11/13 23:03, Jingchao Zhang wrote:
> > Dear all,
> > Today I installed the SSL module for our local Galaxy instance and the
> > "https://" link is working fine. I added this
> > "<Location"/">
> > RequestHeader set X-URL-SCHEME https
> > </Location>"
> > in our Apache configuration file as instructed in this webpage:
> > http://wiki.galaxyproject.org/Admin/Config/Apache%20Proxy
> > Here are my problems with SSL:
> > 1. Some build in links like "UCSC Main
> > <
> > browser" and "UCSC Test
> > <
> > browser" become invalid. If I click on them, nothing will happen, as if
> > they are blocked.
> > 2. The old "http" link still works, which I think shouldn't because I
> > added the "RequestHeader ... https" line in Apache configuration. I
> > really want to disable the http link because the new users could be
> > easily led to the old one.
> > Both httpd and Galaxy have been restarted after the changes are made.
> > Since I didn't find any similar threads in the mailist, I hope someone
> > here can help me out with this.
> > Thanks,
> > Jim
> > ___________________________________________________________
> > 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/
> > To search Galaxy mailing lists use the unified search at:
> > http://galaxyproject.org/search/mailinglists/
> Peter Briggs peter.bri...@manchester.ac.uk
> Bioinformatics Core Facility University of Manchester
> B.1083 Michael Smith Bldg Tel: (0161) 2751482
> 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: