[Solved] 4.1.4 406 errors

sip

Well-Known Member
#1
after upgrade to 4.1.4 it started throwing 406 errors for almost all sites. Downgraded to 4.1.3 and everything works fine.

Not sure if 4.1.4 had this mod_sec behavior built in. 4.1.3 has no such issues. So downgraded.
 

justme

Well-Known Member
#2
In my case, No 4.1.x works with wordpress publishing.. 4.1.2 or 3 would stall uploads, 4.1.4 returns a 403. Back to 4.0.20.
Setup: php-fpm with xcache on linux x86_64.
 

justme

Well-Known Member
#4
I used to compile php lsapi but got tired to manually patch after each release, specially seeing that php-fpm/fastcgi is as fast as lsapi (at least for my needs).
 

mistwang

LiteSpeed Staff
#5
Please do force reinstall of 4.1.4, it should be addressed now.
Scan request body is enabled by default in 4.1.4, while it was disable in Apache and earlier release of LSWS.
 

justme

Well-Known Member
#6
Not fixed after a force reinstall. You really should consider adding a .x to patches versions so one can be sure of what he's running.
 

mistwang

LiteSpeed Staff
#7
Please switch back to Apache to verify if apache mod_security does the same.
Changing release number for each build is a big overhead.
We will release a new release package after we confirmed that all known bugs have been successfully fixed.
 

sip

Well-Known Member
#8
406 errors fixed.

Thanks.

Please switch back to Apache to verify if apache mod_security does the same.
Changing release number for each build is a big overhead.
We will release a new release package after we confirmed that all known bugs have been successfully fixed.
 
Top