Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global response headers #248

Merged
merged 12 commits into from
Jun 2, 2021
Merged

Global response headers #248

merged 12 commits into from
Jun 2, 2021

Conversation

alex-schneider
Copy link
Contributor

No description provided.

@alex-schneider alex-schneider force-pushed the global-response-headers branch from 514b72a to 7235405 Compare May 31, 2021 09:09
@malud malud force-pushed the global-response-headers branch from 7235405 to 3971fd6 Compare June 2, 2021 06:56
Copy link
Collaborator

@malud malud left a comment

Choose a reason for hiding this comment

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

LGTM. Please apply the suggestion regarding the gzip writer.

@@ -93,3 +96,5 @@ func ModifyAcceptEncoding(header http.Header) {
header.Del(AcceptEncodingHeader)
}
}

func (g *Gzip) AddModifier(_ *eval.Context, _ []hcl.Body) {}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Should be removed here. Just define this Method as own interface instead of using the writer if required. As I can see, there are explicit type assertions instead of using the writer interface.

@malud malud force-pushed the global-response-headers branch from 560ce34 to 7c2035e Compare June 2, 2021 11:31
@malud malud merged commit b26ccb1 into master Jun 2, 2021
@malud malud deleted the global-response-headers branch June 2, 2021 11:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants