-
Notifications
You must be signed in to change notification settings - Fork 13
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
Feature/removing accept encoding header when using symfony http client #37
base: main
Are you sure you want to change the base?
Conversation
# # Hier eventueel een uitleg over de wijziging ten op zichte van de # vorige versie max. 72 tekens per regel. # # Eventuele breaking changes hier vermelden en ook verwijzingen naar # tickets en andere resources. # Jira #WST-123 # Zie ook: http://podio.com/webstores/klant/stories/432
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
💚 CLA has been signed |
…using-symfony-http-client
I made some suggestions here on possible cleaner ways to fix this issue. The solution presented in this PR isn't bad, but what if it was made into a "whitelist" (or blacklist) of clients instead of being hard coded just to check for Symfony? Obviously that could get messy and turn into a maintenance headache but it may be better than the current state which appears to be causing confusion and support tickets |
This PR removing the Accept-Encoding: gzip header when using the Symfony HTTP client.
This is needed due to the Symfony behaviour reported here.
This is the same issue like here.