2009/1/12 Nate Coraor nate@bx.psu.edu:
James Casbon wrote:
No it won't. So we either need an explicit exception to the URL-SCHEME code, or to do some more apache trickery to put non https traffic over the same port, just for the ucsc clients.
That's probably a task for a packet filter (firewall) rather than Apache.
I'm not clear on what this would be necessary for, though? UCSC will already talk to your Galaxy over http if you configure Apache to allow it. All other connections would have to use https as long as you use Deny statements in your http vhost to prevent non-UCSC sites from connecting.
I want the table browser to work and generate the correct (https) links back to my galaxy install, which means I set the URL scheme so that these are correct. This has the side effect that links to the tracks for genome browser are also https, which doesn't work. What I need is:
1. https urls for the table browser 2. http urls for the tracks
one is going to be wrong at the moment, because galaxy behaves correctly, but UCSC doesn't.
cheers, James