-
Notifications
You must be signed in to change notification settings - Fork 240
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] Can't include Correlation Header on IE can fail #1260
Comments
On investigating the criteria that is used when the SDK adds this value to the ajax request it appears that there has been a change in IE (as the SDK code around this has not change in over 8 months) where when an ajax request is created it checks that the ajax request is being sent to the same host and if not it does not include -- this IS what is happening here. On doing some basic investigation using https protocol what is occurring is that (for example) when the host is "https://mydomain.com" and an ajax request is sent to "https://mydomain.com/api" when we query the URL for the ajax "host" IE returns "mydomain.com:443" and for the page it returns "mydomain.com" -- which don't match (as we support and verify different ports). As a workaround for this issue you should be able to add the "correlationHeaderDomains" config to the Application Insights config (same place as the Instrumentation key) So for a site hosted on "mydomain.com" using https should add something like the following. aiConfig = { |
[BUG] ajax.ts is using string trim() which is not supported on IE7/8 #1251
Included in v 2.5.5 which is now fully deployed |
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. |
The following function in Utils.ts
const requestHost = UrlHelper.parseUrl(requestUrl).host.toLowerCase();
On IE can return the port number with the host rather than just the host.
Note: This may not be a significant issue or it only affects situations where the ajax request is using a different protocol (http/https/port) than the main hosting page -- investigating.
The text was updated successfully, but these errors were encountered: