AFAIK the semantics of HTTP/2 and HTTP/3 are the same, so no, but both /2 and /3 are able to multiplex these requests, with shared compressed header elements for example, onto a single underlying 'connection'.
I have NGINX -> Gunicorn (Python) -> Experimental WSGI App (Python) serving a website.
A hit from my cellphone initiated that type of request and it caused a strange error. I was able to identify the issue and successfully guessed it was asking me to yield these resources in that specific order.
Now "devtools" shows its HTTP/3.
My load time improved too. The homepage loads < 200ms and its self-hosted on an old Pixelbook.
Comments
AFAIK the semantics of HTTP/2 and HTTP/3 are the same, so no, but both /2 and /3 are able to multiplex these requests, with shared compressed header elements for example, onto a single underlying 'connection'.
Hmmm.
I have NGINX -> Gunicorn (Python) -> Experimental WSGI App (Python) serving a website.
A hit from my cellphone initiated that type of request and it caused a strange error. I was able to identify the issue and successfully guessed it was asking me to yield these resources in that specific order.
Now "devtools" shows its HTTP/3.
My load time improved too. The homepage loads < 200ms and its self-hosted on an old Pixelbook.