Skip to content

[8.2] [Maps] Use content-encoding header from ES for mvt response (#130417)#130431

Merged
nickpeihl merged 1 commit intoelastic:8.2from
nickpeihl:backport/8.2/pr-130417
Apr 16, 2022
Merged

[8.2] [Maps] Use content-encoding header from ES for mvt response (#130417)#130431
nickpeihl merged 1 commit intoelastic:8.2from
nickpeihl:backport/8.2/pr-130417

Conversation

@nickpeihl
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 8.2:

Questions ?

Please refer to the Backport tool documentation

…130417)

* Use content-encoding header from ES for mvt

We can't always assume the content-encoding will be gzip. When SSL is enabled in Elasticsearch, the http.compression is disabled by default. We can use the headers from the Elasticsearch response to form the Kibana response.

You should have HTTPS enabled to test this PR. Use `yarn es snapshot --ssl` and `yarn start --ssl`.

(cherry picked from commit ac5aca4)
@nickpeihl nickpeihl added the backport This PR is a backport of another PR label Apr 16, 2022
@nickpeihl nickpeihl enabled auto-merge (squash) April 16, 2022 14:56
@kibana-ci
Copy link
Copy Markdown

💚 Build Succeeded

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@nickpeihl nickpeihl merged commit 16c6f33 into elastic:8.2 Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants