411 error returned when calling _api/contextinfo

[shibu-123]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

SharePoint REST API

Developer environment

Windows

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

Chrome version : Version 92.0.4515.107 (Official Build) (64-bit)
SPFX - 1.6.0

Describe the bug / error

We have a form built using SPFX solution. On save or submit action sharepoint rest api is invoked.

When user clicks on save or submit the form get stuck and does not perform any action. On the browser console log we could see 411 error returned (content length required) on the rest api _api/ContextInfo request(screenshot attached).

We tried in chrome, edge and mozilla browser all shows the same result. In some blogs, there were solutions to add content-length:0 in the header. But this value is been automatically been added by all the major browsers if there is no content in post request.

We tried clearing browser cache and clearing cookies. All these resolution failed. Any suggestion on how to resolve this issue ?

Steps to reproduce

The issue happened to a particular user and he did a recent windows update in win 10 machine. Post that when he tries to submit a form. the browser does not respond and in the console log he gets 411 error issue

Expected behavior

411 error on the _api/ContextInfo rest api request.

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[patmill]

Who is making the call to ContextInfo?

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.