Add optional headers to DownloadableFile messages when downloading files #306
+42
−3
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.
Fixes #299
This PR implements the recent specification change that allows for optional headers in the DownloadableFile message, which can be used during file downloads to support authentication and other header-based configurations.
The downloadFile function in the packagesSyncer struct has been modified to include optional headers from the DownloadableFile message. This enhancement allows Agents to set custom HTTP headers when downloading files from the server. For instance, headers such as Authorization can now be included to facilitate secure downloads.
Changes Made:
-Updated the downloadFile method to check for the presence of optional headers in the DownloadableFile message.
-Added logic to incorporate these headers into the HTTP request when downloading files.
-Ensured compatibility with the updated protocol specification that outlines the use of headers for authentication and other purposes.