-
Notifications
You must be signed in to change notification settings - Fork 239
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] Using App Insights connection string leads to double slash #2163
Comments
MSNev
added
the
investigation required
Further investigation or discussions required
label
Sep 25, 2023
@siyuniu-ms this seems vaguely familiar can you please check if this has been addressed in later v2.x and v3.x releases and if not we will schedule work to sanitize the inbound connection string. |
The problem could be reproduced in current v3.x. A task is made to fix this bug. |
siyuniu-ms
added
fixed - waiting release
PR Committed and waiting deployment
and removed
investigation required
Further investigation or discussions required
labels
Oct 17, 2023
Fixed and released with v3.0.4, waiting for backporting to 2.8.x |
MSNev
added a commit
that referenced
this issue
Feb 6, 2024
MSNev
added a commit
that referenced
this issue
Feb 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description/Screenshot
When using an Application Insights connection string, the tracking url contains a double forward slash. This is an issue because it conflicts with our CSP headers:
Of course we can whitelist the url with the double forward slash but I think this should rather be fixed at the source.
Steps to Reproduce
Expected behavior
Requests are made with a single forward slash
Additional context
The text was updated successfully, but these errors were encountered: