You can use https. We are probably going to get a trusted SSH certificate set up soon. You might have a way to create an exception for our URL in the meantime via configuration of your browser or OS.
As far as loading mulitple tracks, simply create a text document that lists each track in turn like this, and then do your usual trick to cause that url to get loaded. The customtrack loader can include other URLs, somewhat analogously to the C include files. Simply list the ones you want to be loaded together: Here is an example of the text my page contains: https:/user:passw...@server/mycustomtrack1 https:/user:passw...@server/mycustomtrack2 https:/user:passw...@server/mycustomtrack3 The user and password are optional depending on your use. However the point is that you can simply make a list, and it will recursively fetch anything that starts with http://, https://, or ftp://. -Galt Ar 6/17/2010 4:31 AM, scríobh Maxim: > Hi, > > I managed to display remote BigWig files hosted on my Server in UCSC > Browser. Right now I have a simple HTML document displaying the links. > As there are multiple files, the user has to click the individual > link, then go back and hit the others one by one. Recently I came > across a mailing list thread that explained that there is a way to > upload multiple files at once. As far as I remember, you have to > generate a text file that includes all the given URLs. Unfortunately > after many hours searching (I obviously have cleared my Browser cache > in between) I still cannot find this post. On the long run I'd like to > have a little Website with radiobuttons next to the respective > filenames present in the given folder so the user can just click what > he/she likes to see and batch upload everything selected. > > Is this possible at all? > > Additionally the files are in a password protected folder. I've > learned how to pass the login details with the URL link but wonder how > to protect the links. What will I have to do in order to use https > instead of http. Just providing https in the URL results in a browser > failure that the certificate cannot be trusted. > > Best regards > Maxim > _______________________________________________ > Genome maillist - [email protected] > https://lists.soe.ucsc.edu/mailman/listinfo/genome _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
