Skip to content

X-Requested-With header is incorrect in FetchHttpClient #44933

@val1984

Description

@val1984

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs: Author FeedbackThe author of this issue needs to respond in order for us to continue investigating this issue.Status: No Recent Activityarea-signalrIncludes: SignalR clients and servers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions