Ive had to roll back from testing lsws5 because of problems with the http/2 implementation.
either it crashes the whole litespeed process sometimes when http2 is involved. ive forwarded the bug reports onto lsws, but with no reply.
and today we've noticed on a small production environment that several 301 and 302 responses are resulting in 403 errors in browser, but only when browsing the site with https (and so using http/2).
there were no new entries in the lsws logs upon each error so i actually suspect it might be chrome at fault?
either it crashes the whole litespeed process sometimes when http2 is involved. ive forwarded the bug reports onto lsws, but with no reply.
and today we've noticed on a small production environment that several 301 and 302 responses are resulting in 403 errors in browser, but only when browsing the site with https (and so using http/2).
there were no new entries in the lsws logs upon each error so i actually suspect it might be chrome at fault?