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

[BUG] Response compression not enabled on new CDN endpoint #1464

Closed
harvey-k opened this issue Jan 24, 2021 · 4 comments
Closed

[BUG] Response compression not enabled on new CDN endpoint #1464

harvey-k opened this issue Jan 24, 2021 · 4 comments
Assignees
Labels

Comments

@harvey-k
Copy link

Steps to Reproduce

Requesting the application insights bundle from the legacy endpoint returns a compressed response:
https://az416426.vo.msecnd.net/scripts/b/ai.2.min.js
content-encoding gzip
content-length 37648

Requesting the bundle from the new endpoint does not return a compressed response:
https://js.monitor.azure.com/scripts/b/ai.2.min.js
content-length 126996

Expected behavior
The js.monitor.azure.com endpoint should support response compression.

@MSNev MSNev self-assigned this Jan 25, 2021
@MSNev MSNev added the p1 label Jan 25, 2021
@MSNev
Copy link
Collaborator

MSNev commented Jan 25, 2021

Hi @harvey-k, I've tracked down the issue to a problem with one of our CDN endpoints (which was the primary), I've just switched the provider used for this endpoint (as manual testing should that it was working). It may take up to 5 minutes (depending on your DNS cache and provider) before the change is reflected.

@MSNev
Copy link
Collaborator

MSNev commented Jan 25, 2021

So js.monitor.azure.com should be serving the compressed version shortly, additionally we also just release v2.5.11 to the CDN (not related to this issue -- just timing)

@harvey-k
Copy link
Author

@MSNev Wonderful, thank you for your help!

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants