Question about http3

Started by Labionda, Oct 17, 2022, 01:22 PM

Previous topic - Next topic

LabiondaTopic starter

I think at New Year holidays (when there is minimum traffic) to update server software and at the same time I think to switch from http2 to http3. And I can not google this question.

Now if my browser does not support http2, - then the connection by default goes to http 1/1, and how will it be if you configure http3?

If the browser does not support http3 connection will be http2 or http 1/1?
!أطيب التمنيات
  •  

Newport

Quote from: Labionda on Oct 17, 2022, 01:22 PMIf the browser does not support http3 connection will be http2 or http 1/1?

If all is well set up (although so far all that is associated with quic (http3) is a beta-test) then you will have a new protocol on udp and old on tcp.
And everything will be available both in the new and old browsers.
  •  

LabiondaTopic starter

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.
!أطيب التمنيات
  •  

-DM-

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...
  •  

LabiondaTopic starter

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!
!أطيب التمنيات
  •  

Newport

-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.
  •  

Bronson

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.
  •  

-DM-

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.
  •  

Guess jr.

I tested http3, I put version from nginx (https://quic.nginx.org/readme.html), there is also version from cloudflare. As you specify in the settings, so everything will work.
If you specify 2 protocols - both will work. If you specify one protocol - only one will work.
You can check if the protocols work by opening/closing udp.
  •  

tamilabi

Regarding disputes over closed UDP ports, this problem is not great and does not have a relative global character.
Those who have closed all UDP ports except 53 will have to go to their terminal hardware (firewall, router) and open one conditional port - 5335/UDP for example. And providers on switches and routers / L3 (and these are millions of intermediate devices) do not need to do this (problems will only affect the shit with prohibitive installations like China and.. which).

That is, deploying the protocol at the global level, on top of UDP costs nothing, however, administrators of end networks (home, corporate), if they have closed all UDP ports, will have to go to their router/firewall and open one port.
For this, enterprises pay admins, and honest admins, if they have closed something on their home router, then they will figure out how to open one "berth" for this locomotive.
  •