Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Fall 7 Dec 14 - Dec 23, Spring 1 2021 Mar 22 - Apr 2, Spring 2 2021 Apr 5 - Apr 16, Spring 6 2022 Mar 14 - Mar 25
Description
A lot of Web sites are configured to redirect http to https for most URLs.
However, it is not clear how IGB handles this when accessing Quickload URLs.
For example, what happens if IGB tries to contact a site added to IGB as Quickload URL "http://example.com/quickload" and the server is configured to redirect request to "https://example.com/quickload" ?
Can IGB properly handle the redirect?
Please investigate.
Possible strategy:
- Add an all-new testing Quickload site to BioViz.org (e.g., http://bioviz.org/example_quickload), submit PR for the example and wait for it to merged and deployed
- Confirm that the redirection is working by opening the "contents.txt" URL in a browser (http://bioviz.org/example_quickload/contents.txt)
- Deactivate all current Quickload sites in IGB and then re-start IGB
- Next, add this new Quickload testing URL to IGB using protocol "http" as the quickload address
- Then try to open the genome from the testing site in IGB
- Report any errors observed.
Does IGB appear to be reading and using the testing quickload meta-data files to configure the genome?
Report on any errors.
