Hack for HTTPS support for Genome Browser
Hi, The files "intervals.py" and "genetics.py" in "/lib/galaxy/datatypes/" contains "hacks" for turning HTTPS into HTTP because the genome-browser didn't support https. I think that recent versions of the genome browser do support HTTPS (at least there's an option for that in the source code), so this hack can be removed, -gordon
Assaf Gordon wrote:
Hi,
The files "intervals.py" and "genetics.py" in "/lib/galaxy/datatypes/" contains "hacks" for turning HTTPS into HTTP because the genome-browser didn't support https.
I think that recent versions of the genome browser do support HTTPS (at least there's an option for that in the source code), so this hack can be removed,
It looks like it does negotiate SSL properly but doesn't handle the response (it's reading all of the response, including the headers, as the content)? My attempt to view on UCSC Main and Test resulted in: Unrecognized format line 1 of https://example.org/root/display_as?id=2&display_app=ucsc&authz_method=display_at: HTTP/1.1 200 OK (note: chrom names are case sensitive) The same dataset served through HTTP works fine. I double checked that the content type is set correctly on both schemes. Perhaps someone from UCSC on the list can comment on whether SSL for hgt.customText is supported or still in development? Thanks, --nate
-gordon _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
participants (2)
-
Assaf Gordon
-
Nate Coraor