Fix CORS error when using library with Browserify #213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Customers are starting to use the AppInsights node.js SDK to develop browser applications thanks to browserify. This creates a shim for any http.request and https.request call so it redirects to XMLHttpRequest. Unforutnately, this shim defaults to setting withCredentials.
This specific setting does not like the wildcard value for the
Access-Control-Allow-Origin
header.Browserify code that causes the problem, that has not been fixed for about 2.5 years now.
Recommended that we add an explicit
withCredentials = false
in the sender library to avoid these exceptions.