The syntax is is: protocol://encoded-user:[email protected]/somepath
So the @ here sign is important part of the syntax when specifying user and password in a URL and should not itself be encoded. But the username and the userpassword do need to be encoded if they contain any special characters. -Galt 8/17/2010 11:12 AM, Jennifer Jackson: > Hello Scott, > > When using names/passwords in the bigDataUrl, some characters need to be > "escaped" as hexidecimal. Specifically for your case, change the "@" to > be "%40". > > This is noted at the bottom of the custom track submission form, but > here it is, for quick reference: > > If a login and password is required to access data loaded through a URL, > this information can be included in the URL using the format > protocol://user:[email protected]/somepath. Only Basic Authentication > is supported for HTTP. Note that passwords included in URLs are not > protected. If a password contains a non-alphanumeric character, such as > @, the character must be replaced by the hexidecimal representation for > that character. For example, in the password my...@wk, the @ character > should be replaced by %40, resulting in the modified password mypwd%40wk. > > Please feel free to contact the mailing list support team again if you > would like more assistance. > > Warm regards, > > Jen > UCSC Genome Browser Support > > On 8/16/10 11:51 PM, Scott Alexander Lindsay wrote: >> Hi, >> >> I am trying to view some data as a custom track. I converted a wiggle >> file to bigWig format using the wigToBigWig tool, that seemed to go >> okay, I did't get any error messages. I just tried to add it as a >> track, and I got the following error: - >> >> Error ftp server error on cmd=[SIZE /lane2_tophat_gff.bw ] >> response=[550 /lane2_tophat_gff.bw: not a plain file. ] Couldn't open >> ftp://myusername:[email protected]/lane2_tophat_gff.bw >> >> I used >> 'bigDataUrl=ftp://myusername:[email protected]/lane2_tophat_out_gff.bw' >> to describe where to get the file from. >> If I type that into a browser, the file downloads fine. >> >> I looked at the file in question and it does look quite strange, lots >> of strange characters, definitely not human-readable! Here is a bit >> of it : - >> >> &¸èà€ >> >> >> Ä >> ¯ >> >> 5J >> · >> Ö >> ˚ >> ˙ >> >> ‡;· >> ˚ >> >> µb >> ˝ >> >> ÄÔ >> 1 >> {˝ >> >> Ê >> >> ˛ >> >> æ >> >> 2 >> '˛ >> >> ,L >> ˛ >> >> ¢˛Is this normal? I read that the wigToBigWig program creates an >> indexed binary file, and assumed that this was what I was seeing. >> >> Thank you, >> >> Scott >> _______________________________________________ >> Genome maillist - [email protected] >> https://lists.soe.ucsc.edu/mailman/listinfo/genome > _______________________________________________ > Genome maillist - [email protected] > https://lists.soe.ucsc.edu/mailman/listinfo/genome _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
