ASP.NET
A set of technologies in the .NET Framework for building web applications and XML web services.
3,243 questions
Why does ASP.NET Web API incoming request have the br encoding removed from the header
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 86%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Peterjc
81
Reputation points
Hi, I am sending a request (in this case happens to be via an Angular client - but I think that is irrelevant) to my ASP.NET Web API server (running on .NET Framework 4.8). Both client and server are running on my Windows 11 dev machine.
When I look at this in the browser (Chrome) devtools, it has Accept-Encoding: gzip, deflate, br
However, if I put a break point in my server's controller, and look at it's Request object in the debugger, the br seems to be gone
I was looking at adding a Brotli compression for my responses, but if the header is not asking for it, then no point.
Does anyone know why this is missing form the header once it gets to the server?
Thanks in advance
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 4%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EQM%3C/text%3E%3C/svg%3E)
QiYou-MSFT 4,306 Reputation points Microsoft Vendor2023-03-31T07:54:56.3533333+00:00 Hi @Peterjc
I did a simple test and found that asp.net webAPI supports this compression mode (nothing was added to the initial project).
If you have made any other changes, if you can give me more details so that I can reproduce the problem, I can better help you solve the problem.
Best Regards
Qi You
-
Peterjc 81 Reputation points
2023-04-07T02:30:32.7666667+00:00 Hi thanks for for looking into this. Was your above application running .net 4.8 framework? This is what we are currently still on in the two asp.net Web API servers we have that get this behavior.
-
QiYou-MSFT 4,306 Reputation points Microsoft Vendor
2023-04-07T09:52:59.4433333+00:00
Sign in to comment