What’s new in .NET 9?
.NET 9 brings a number of performance improvements and minor changes. However, this version doesn't bring much to the table that it radically changes the way we write code. In this, the 3 previous versions were sufficiently implemented. Even one more significant change – implicit extension types, which had the potential to significantly change the way we write code, was eventually removed from C# 13 and will probably not see it for a year. Read more ›
What’s new in .NET 7?
Although .NET 7 brings another number of new features, the main emphasis this time was on performance. ASP.NET contains rate limiter, so we can usually do without the web.config file. The 11th version of C# brings better work with strings. And one feature that was previously only available in UWP and Mono – compilation in AOT mode (ahead-of-time) – is now available for the entire framework. Read more ›
What’s new in .NET 6?
.NET 6 completes the alignment with mobile and desktop development. It introduces the so-called Target framework moniker (TFM), which specifies that the project targets a specific SDK. For example, iOS targeting is written as net6.0-ios. Previously, TFM described a specific version. NET or its clone modified for a specific platform. But that is changing now. All platforms share a single .NET and the specific platform-specific API that is accessible through the SDK is listed after the dash. Read more ›
Browsers Will Freeze its User-Agent Strings
The User-Agent HTTP header was introduced in 1993 by the first web browser. The string was as simple as Mosaic/0.9. It could be used for good purposes. Web servers can serve slightly different content to browsers that might implement new standards differently. Sadly, Google is abusing its dominant position by blocking or malfunctioning its services for competitive browsers. Therefore, a new mechanism for declaring the technical aspects of a user’s device is emerging. Read more ›
What to Expect from HTTP/3
We barely deployed HTTP/2 and we are already talking about HTTP/3. The web is moving very fast these days and its users will benefit from that. In fact, Chrome is already using HTTP/3 if you are connecting to Google’s servers. The protocol has been in development and tested in production environments for years under the name QUIC. It surpasses TCP and is built entirely on UDP. And the best part – encryption is mandatory (at least for the time being). Read more ›
How to redirect to HTTPS in ASP.NET MVC application correctly
Upgrading browsers visiting your website to a secure connection is a best practice and is easy to do. I have decided to share my implementation because I have seen many partial or insecure implementations. Correct implementation satisfies both backward compatibility and security requirements of various web browsers. This article covers what you need to know before you start redirecting your users to the HTTPS protocol. Read more ›
How to Enable Response Compression in ASP.NET Core 2 With gzip and Brotli Encoding
Internet traffic can be compressed to save network bandwidth usage. While images and web fonts are already compressed, text files are stored on the server in human-readable form. HTTP.sys server and Kestrel currently don't have built-in compression support. By default, only static files are compressed with gzip. What if you want to compress more? Read more ›
Internet Explorer supports HTTP Strict Transport Security
HTTP Strict Transport Security (HSTS) provides decent defense against man-in-the-middle attacks. All the server has to do is send a certain header, and the browser will only establish a connection with it via TLS. There will then be no connection anywhere that is unencrypted and allows an attacker controlling network traffic to unknowingly redirect users to a fraudulent site. Today’s update (3058515) adds HSTS support to Internet Explorer 11 for Windows 7 and Windows 8.1. Read more ›
Internet Explorer changes the User-Agent string again
Yesterday, a new build of Windows 10 preview was released, which includes Internet Explorer having quite a lot of what is being prepared for IE 12. A significant new feature is another change in the string that is used in the HTTP protocol to identify the browser. Recall that IE 11 removed compatible and MSIE. IE 12 will go even further and remove Trident. On the contrary, it adds Edge. As a result, some systems recognize IE 12 as Chrome. This is a purpose because a lot of IE developers have blocked modern tech. Read more ›
Internet Explorer starts supporting HTTP/2
Internet Explorer 11 in Windows 10 Technical Preview supports HTTP 2.0, now called HTTP/2. However, this is not some shallow term, like the previously so popular Web 2.0 that marketers used to use when they wanted to express "Myslíme si, že umíme psát weby lépe, než vy." It will bring faster page load times and new information will appear as soon as it is available. And if browser manufacturers succeed in enforcing this, all traffic will also be encrypted. Read more ›
IE in Windows Phone 8.1 has a new User-Agent string
Not all websites are responsive yet, and many of them have two more versions. One for desktop computers, the other for portable devices. The algorithms that ensure that the portable version is displayed on the phone contain bugs. IE therefore has no choice but to adapt to these errors. But there is no other way than to change your face and pretend to be a different browser. Users will feel the change for the better, while the loudest protests will be those developers who caused the whole situation by ignoring IE. Read more ›
IE11 has a new User-Agent string
Internet Explorer 11 differs from previous versions, among other things, in several important details. One of them is to change the string that the browser identifies itself and that it sends in each HTTP request. While in previous versions the changes were conservative and more or less only the version number was changed, now the identifier MSIE has been removed and the note like Gecko has been added. As a result, some systems recognize IE 11 as Firefox. Read more ›