ASP.NET Core 3, IIS and empty HTTP headers
Read OriginalThe article details a specific issue encountered when upgrading an ASP.NET Core 2.1 WOPI host to version 3.1, where empty HTTP headers (like X-WOPI-Lock) are silently removed by IIS in-process hosting, causing protocol test failures. It explains the HTTP specification validity of empty headers, traces the problem to a specific code change, and offers a practical workaround involving setting headers to a whitespace string.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
No top articles yet