Add an experimental GCSDownloader for HTTPS Collection support #1342
+431
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an initial experimental implementation, not necessarily our long-term interface.
It solves the most important problem in handling HTTPS for GCS, which is translating a file URL into a collection ID.
The interface is the part most subject to potential future refinement, as it's not clear how to provide the right level of control over
This is an implementation of HTTPS download from GCS collections via
Location header sniffing, which is the only mechanism we have available
on all GCS versions for translating a URL to a client ID.