TechnitiumSoftware
Can compression protocols be added?
Thanks for asking. If you mean to have it for the HTTP services then will get it enabled. However there is no support for ZTSD in kestrel web server yet.
Thanks for asking. If you mean to have it for the HTTP services then will get it enabled. However there is no support for ZTSD in kestrel web server yet.
However, it seems that ASP.NET Core does support it: https://learn.microsoft.com/zh-cn/aspnet/core/performance/response-compression?view=aspnetcore-9.0
Thanks for asking. If you mean to have it for the HTTP services then will get it enabled. However there is no support for ZTSD in kestrel web server yet.
However, it seems that ASP.NET Core does support it: https://learn.microsoft.com/zh-cn/aspnet/core/performance/response-compression?view=aspnetcore-9.0
It supports BR algo but I don't see any mention of ZTSD.
Thanks for asking. If you mean to have it for the HTTP services then will get it enabled. However there is no support for ZTSD in kestrel web server yet.
However, it seems that ASP.NET Core does support it: https://learn.microsoft.com/zh-cn/aspnet/core/performance/response-compression?view=aspnetcore-9.0
It supports BR algo but I don't see any mention of ZTSD.
It seems to be okay as well.
We'll have to wait for .NET 11, to be released on November 2026 according to this issue on dotnet runtime: https://github.com/dotnet/runtime/issues/59591
It would be best to have an option to choose from.
The choice is done automatically by the client using Content-Encoding header in request. So no need to have additional option to configure it.
It would be best to have an option to choose from.
The choice is done automatically by the client using Content-Encoding header in request. So no need to have additional option to configure it.
If it's fine to enable all by default, that would be great. Because I just noticed that HTTP is using gzip 😂
Technitium DNS Server v14.3 is now available which fixes this issue. Do update and let me know your feedback.
Technitium DNS Server v14.3 is now available which fixes this issue. Do update and let me know your feedback.
Is there no BR agreement?
@Potterli20 Its been enabled for the admin web service and not for the DoH web service. Also, your web browser is asking only for gzip and deflate, and probably do not support BR algorithm.
@Potterli20 Its been enabled for the admin web service and not for the DoH web service. Also, your web browser is asking only for gzip and deflate, and probably do not support BR algorithm.
Is there any way to test it out?
I'm using http, not https. I don't know if this is related.
It works for HTTP too.
Is there any way to test it out?
Yes, you use the same web browser development tools when you visit the admin panel. But since your browser supports only gzip and deflate, the server would select gzip in response.
It's okay. I've seen that others have already enabled it all by default. Hahaha
I don't know what the problem is either.
In these screenshots, you are just seeing the request part. You need to see the response headers in the section above it.
See the headers that I see using Firefox browser. Notice that the transferred file size is smaller than the actual file size being downloaded.
See the headers that I see using Firefox browser. Notice that the transferred file size is smaller than the actual file size being downloaded.
I couldn't test it this way. I'm using the podman container and the http protocol.
With HTTP only gzip and deflate algorithms work as seen in my test below:
With HTTP only gzip and deflate algorithms work as seen in my test below:
Then I roughly understand that on http, only the gzip and deflate algorithms are supported. But I only use http.😂😂
With HTTP only gzip and deflate algorithms work as seen in my test below:
Can't all http protocols be enabled by default?
Then I roughly understand that on http, only the gzip and deflate algorithms are supported. But I only use http.😂😂
Ya, on HTTP only gzip and deflate works. For the newer algorithms, HTTPS is required.
Can't all http protocols be enabled by default?
The web server already has them enabled. Its the web browser which has to request for them in Accept-Encoding header. Browsers only use gzip and deflate when sending request to HTTP only URLs so web server has to respond using one of them.
But it's also rather strange. On the Windows 11 Home Edition, open the HTTP protocol separately by default, including Zstd.
But it's also rather strange. On the Windows 11 Home Edition, open the HTTP protocol separately by default, including Zstd.
Some web browsers may have support for it while others not. So its totally client side issue and that the web server has all compression algorithms enabled.
You are testing this with IIS web server so not sure about it and it may need some config to enable those compression algorithms.