Skip to content
This repository was archived by the owner on Dec 21, 2021. It is now read-only.

Set correct content type to HTTP responses #89

Merged
merged 2 commits into from
Oct 19, 2021
Merged

Conversation

siegfriedweber
Copy link
Member

@siegfriedweber siegfriedweber commented Oct 18, 2021

Description

The repositories responded with content type "application/octet-stream" but the Stackable Agent expects now "application/gzip" (see stackabletech/agent#326).

Review Checklist

  • Code contains useful comments

The repositories responded with content type "application/octet-stream"
but the Stackable Agent expects now "application/gzip".
@siegfriedweber
Copy link
Member Author

I changed this pull request to a draft because I missed that the files from the Integration test repo are also served with Content-Type: application/octet-stream.

@siegfriedweber
Copy link
Member Author

This pull request is now waiting for stackabletech/integration-test-commons#32.

maltesander
maltesander previously approved these changes Oct 19, 2021
Copy link
Member

@maltesander maltesander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

soenkeliebau
soenkeliebau previously approved these changes Oct 19, 2021
@siegfriedweber siegfriedweber marked this pull request as ready for review October 19, 2021 08:17
@siegfriedweber siegfriedweber merged commit 1b150ba into main Oct 19, 2021
@siegfriedweber siegfriedweber deleted the fix_content_type branch October 19, 2021 08:56
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants