[Solved] 4.1.4 406 errors

Discussion in 'Bug Reports' started by sip, Aug 28, 2011.

  1. sip

    sip New Member

    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.
  2. justme

    justme Member

    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.
  3. NiteWave

    NiteWave Administrator

    have you tested lsapi php instead of php-fpm?
    it's recommended.
  4. justme

    justme Member

    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).
  5. mistwang

    mistwang LiteSpeed Staff

    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.
  6. justme

    justme Member

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

    mistwang LiteSpeed Staff

    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.
  8. sip

    sip New Member

    406 errors fixed.

    Thanks.

Share This Page