Details
-
Type: Task
-
Status: Closed (View Workflow)
-
Priority: Blocker
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:3
-
Epic Link:
-
Sprint:Summer 5 2022 July 18, Summer 6 2022 Aug 1, Fall 1 2022 Aug 15
Description
Situation: IGB is not able to follow redirects from http to https for quickload meta-data files. This can lead to otherwise valid quickloads being unable to load in IGB. Additional details available in IGBF-2669.
Task: Enable IGB to follow http to https redirect for Quickload meta-data files.
Before starting review these links:
Attachments
Issue Links
- relates to
-
IGBF-3441 Fix DAS error
- Closed
-
IGBF-3204 Create secure quickload that redirects
- Closed
-
IGBF-3199 Fix: local quickload not added as data source
- Closed
-
IGBF-3196 Investigate: Why is the password asked for twice after adding secure data source.
- To-Do
-
IGBF-2669 Investigate: How does IGB handle Quickload URL redirection from http to https
- Closed
Theoretically, if a particular "http" url redirects to "https" or anything else , the status code returned would be 300 series which indicates if the url is moved permanently or temporarily (see HTTP Header Location , HttpURLConnection ). After receiving 300 series response, we can try requesting the "https". However, redirecting it to the location in the response is the ideal option and this would be possible with HttpURLConnection class which is used in Bookmark pipeline to check if the remote file exists. Trying to assess the scope of changes needed and for alternatives just in case