4.2.5 broke "Force Strict Ownership"

Discussion in 'Bug Reports' started by rinogo, Nov 8, 2013.

  1. rinogo

    rinogo New Member

    1) OS type and Version. If using 64bit OS, please note as such.
    Linux xyz.com 2.6.32-042stab078.27 #1 SMP Mon Jul 1 20:48:07 MSK 2013 i686 i686 i386 GNU/Linux

    2) LiteSpeed Version (Version Number + Model: Standard/Enterprise)
    Litespeed Web Server Enterprise v4.2.5

    3) If PHP related: PHP version and interface of choice: FCGI, CGI, or LSAPI.
    Not PHP related.

    4) All possible related info that you observed before and after, the bug occurred. There more info LiteSpeed developers have, the faster we can resolve your issues.
    See below.

    5) If you can reproduce the bug, please detail what the steps are.
    Under 4.2.2, with "Force Strict Ownership" enabled, files were delivered as expected. Immediately after upgrading to 4.2.5, I started seeing 403 errors in the LS log, and some files were not served, but instead generated 403 errors. Reverting to 4.2.2 (with Force Strict Ownership still enabled) fixed the problem. Additionally, using 4.2.5 with Force Strict Ownership causes files to be served as expected. Conclusion: Based off of the release notes that 4.2.5 tweaked the "Force Strict Ownership" setting, 4.2.5 caused a regression in Force Strict Ownership.

    6) Note any errors logged in error.log and stderr.log of LiteSpeed logs directory.
    Example of 403 error:
    2013-11-08 11:35:48.814 [INFO] [x.x.193.4:8184-0#APVH__wildcard_.xyz.net] File not found [/home/xyz/public_html/wp/error/403.html]
    Last edited: Nov 8, 2013
  2. NiteWave

    NiteWave Administrator

    that might be 4.2.2's implement has bug in it.

    can you give an example file which cause this 403 error, its ownership, and should it return 403 ? with this detail information, we can know if it's a 4.2.2 bug or 4.2.5 bug.

Share This Page