-
lovetox
HTTP1 should be fine on most webservers or?
-
lovetox
or is it already so that some servers dont support that anymore?
-
theTedd
I have encountered some that reject HTTP1 requests
-
theTedd
Possibly CloudFlare, or that was coincidental
-
singpolyma
you mean 1.0? Or 1.1?
-
theTedd
0.9, 1.0, 1.1
-
Cynthia
HTTP 0.9 has no headers
-
lovetox
i mean whatever people mean if they say the server does not support HTTP2
-
singpolyma
If 1.0 didn't work that's a bit odd but not a huge shock. If 1.1 doesn't work one may well ask if it counts as a webserver at all
-
singpolyma
HTTP2 is barely HTTP really. It's just some other thing
👍 1 -
lovetox
i enabled http2 support in Gajim a few releases back, since then many users complain that its worse in some way or does not work at all
-
theTedd
Could be websites rejecting anything that doesn't look like a standard (popular) browser request in an attempt to fight LLM crawlers?
-
lovetox
no, we are talking about xmpp http upload servers
-
theTedd
Having links to investigate would really help
-
singpolyma
I'd expect most such to not support http2 but I assume you have fallback
-
lovetox
the problem is with the servers that support http2
-
lovetox
there problems are reported
-
lovetox
im not interested to debug http servers and libraries, i just plan to disable it and go back to http1 only
-
lovetox
the problems are not of the nature "does not work at all" which is probably easy to debug
-
lovetox
the problems are stuff like, "takes 20 seconds longer than usual", "stuck at 100%", or very technical errors from the lib, like some frame windows are not big enough
-
Link Mauve
Oh, I’ve experienced the "stuck at 100%" bug against JabberFR, which uses a very standard nginx with h2 enabled.
-
Link Mauve
So it is an issue of your HTTP library?
-
lovetox
as said, i dont debug http libraries, nor servers