-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Closed
Labels
Needs: Author FeedbackThe author of this issue needs to respond in order for us to continue investigating this issue.The author of this issue needs to respond in order for us to continue investigating this issue.Status: No Recent Activityarea-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and servers
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
FetchHttpClient.ts sets X-Requested-With header to XMLHttpRequest which makes it harder than needed to know which HTTP client was used by @microsoft/signalr JS library.
Expected Behavior
X-Requested-With header should be set to Fetch as it was in the initial implementation.
Steps To Reproduce
Make use of @microsoft/signalr JS library and check the headers sent by the lib when calling the negotiate route.
Exceptions (if any)
No response
.NET Version
No response
Anything else?
@microsoft/signalr: ^6.0.9
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Needs: Author FeedbackThe author of this issue needs to respond in order for us to continue investigating this issue.The author of this issue needs to respond in order for us to continue investigating this issue.Status: No Recent Activityarea-signalrIncludes: SignalR clients and serversIncludes: SignalR clients and servers