Details
-
Type: Task
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:1
-
Epic Link:
-
Sprint:Fall 1 2021 Aug 16 - Aug 27, Fall 2 2021 Aug 30 - Sep10
Description
Validating trackhub URLs is currently done in the browser and involves making requests for their content and ensuring that it conforms to the UCSC trackhub specification. The UCSC CORS policy does not allow websites to make these requests, however. Implement a work-around.
Possibilities:
- See if the UCSC API can be used to validate a trackhub.
- Implement a validation endpoint on our hub facade API.
- Use a public CORS proxy to forward browser requests.
Attachments
Issue Links
- relates to
-
IGBF-2898 Add listing of UCSC hubs to the bioviz trackhubs page
- Closed
I was able to find a UCSC API endpoint that can be used to validate track hubs. Please see my changes here.
I tested this with both track hubs in UCSC public list as well as others that I found online e.g.