During the New Year holidays, which typically have less traffic, I plan to update our server software. Additionally, I am considering a switch from http2 to http3, but I have been unable to find information on this topic through online research.
Assuming that my browser does not support http2, it will default to connecting via http 1/1. However, I am curious about the connection setup if we were to configure http3. If a browser does not support http3, what connection will be established - http2 or http 1/1?
On a related note, it may be worth considering the potential benefits and drawbacks of switching to http3, such as improved speed and security versus potential compatibility issues.
Assuming proper configuration, which is currently in beta testing for quic (http3), a new protocol will be available on udp while the old protocol will remain on tcp. This means that access to both protocols will be available on newer and older browsers alike.
It's interesting to note that this new protocol could potentially offer improved speed and security compared to the old protocol. However, it remains to be seen how widely adopted and supported it will become.
If http3 is not available, will you try to connect to http2, or 1.1?
All the same, the technology is still in beta-test, how soon will be perfected...
Not to make irreparable mistakes.
And what prevents you from just create a subdomain, and test everything you can?
No, it's easier to sit around for 24 hours, polemics about nothing.
The New Year is still far away...
Quote from: -DM- on Oct 18, 2022, 04:20 AMAnd what prevents you from just create a subdomain,
Well, yes, the logic is ironclad. :) Let's buy hosting, kill a lot of time to configure, to check such nonsense, instead of asking...
Nothing to answer, - please pass by!
-DM- advised you correctly. You can understand a lot of questions by "live" testing.
There are problems which will not be described here.
For example with http2, when it reappears after a connection failure, the pictures may be under-loaded.
I've often seen this problem in practice on WS. Then they fixed it.
Quote from: Labionda on Oct 18, 2022, 04:41 AMWell, yes, the logic is ironclad. :) Let's buy hosting, kill a lot of time to configure, to check such nonsense, instead of asking...
Nothing to answer, - please pass by!
Why ask about the technology, which is in beta test? It has a lot of bugs and how it behaves, - no one knows in one situation or another (this beta test, a lot of bugs). And most importantly, IMHO, requires upgrading the hardware at the providers to work http3.
My opinion: too early to use http3, that's like five years from now, you can start trying.
Now only http2 went to the "full".
Well, for interest, of course, can be tested - maybe the benefits of this for the community will be. Server with "combat" sites should not be transferred.
I have conducted tests on http3 using the nginx version (https://quic.nginx.org/readme.html), although there is also a version available from cloudflare. As long as the correct settings are specified, the protocol will function properly.
It's important to note that if two protocols are specified, both will work. Conversely, if only one protocol is specified, only that one will work. To check whether the protocols are working correctly, simply open and close udp connections.
Overall, it seems that migrating to http3 is a promising option for potentially improving website speed and security. However, it's important to ensure proper configuration and testing before fully implementing this new protocol.
Disputes over closed UDP ports are not a major issue and do not have significant global implications. However, those who have closed all UDP ports except for 53 will need to manually open a conditional port such as 5335/UDP on their terminal hardware (firewall, router).
It's worth noting that deploying the protocol globally on top of UDP incurs negligible costs. Only administrators of end networks (home or corporate) who have closed all UDP ports may need to take extra measures to open a single port. In these cases, enterprises pay administrators to handle these types of issues. Honest administrators should be able to figure out how to open a "berth" on their home router for this purpose.
Overall, while there may be minor technical hurdles to overcome when implementing http3, the potential benefits in terms of improved website speed and security make it a worthwhile consideration for website owners and administrators.
Considering the switch from http2 to http3 involves several technical and practical considerations. When updating server software during the holiday period, it's essential to ensure that the process is well-planned and tested thoroughly to minimize any potential disruptions to service.
Regarding the connection setup, if a browser does not support http3, it will fall back to either http2 or http 1/1, depending on the browser's capabilities and configuration. This fallback mechanism is crucial to maintaining compatibility with a wide range of user devices and browsers.
When evaluating the potential benefits and drawbacks of switching to http3, it's important to consider the technical improvements it offers. HTTP/3, based on the QUIC protocol, aims to provide faster and more secure communication between clients and servers. It addresses some of the performance limitations of http2, especially for high-latency connections and packet loss scenarios. However, as with any technology transition, there are potential drawbacks to consider. One of the primary concerns is the current level of browser support. While major browsers are working to implement http3 support, not all users may have access to a compatible browser in the near term.
Furthermore, it's crucial to weigh the benefits of improved speed and security against potential compatibility issues. If a significant portion of your user base relies on browsers that do not support http3, this transition could lead to a degraded experience for those users. Thorough testing and monitoring are essential to identify and address any compatibility issues before fully committing to the switch.
Updating server software is a strategic decision, and the potential switch to http3 offers technical benefits. However, careful consideration of user compatibility and thorough testing are essential to ensure a smooth and positive experience for all users.
When it comes to HTTP/3, if a browser doesn't support it, it will fall back to using HTTP/2. However, if a browser doesn't support HTTP/2, it will default to using HTTP/1.1. This is because HTTP/3 is built upon the QUIC (Quick UDP Internet Connections) protocol, which is designed to provide better performance and security. QUIC is a UDP-based protocol, whereas HTTP/2 is built on top of TCP.
Now, regarding the benefits and drawbacks of switching to HTTP/3, it's essential to consider the potential trade-offs. On the plus side, HTTP/3 promises improved speed and security due to its use of QUIC, which provides better connection establishment and multiplexing capabilities. Additionally, QUIC's use of UDP instead of TCP can reduce latency and improve packet loss resilience.
However, there are some potential drawbacks to consider. For instance, HTTP/3 is still a relatively new standard, and browser support is limited. Additionally, some older devices or networks may not support QUIC, which could lead to compatibility issues. Furthermore, the increased complexity of QUIC may introduce additional security risks if not properly implemented.