WordPress.org

1. ultradust
   Member
   Posted 4 months ago #

   For about a year, I had WP Super Cache installed on a site which is managed under version control and staging practices. It was working as expected. (Re: the version control - I must demonstrate the site's functionality on our dev site prior to deploying to staging and production.)

   Our dev and staging environments are password protected via Windows Authentication. I updated to the latest version of WP Super Cache and the latest version of WordPress and I discovered today that, when running Super Cache on those environments, I now get 500 errors.

   If I turn Windows Authentication off (allowing Anonymous Authentication), Super Cache works perfectly. As soon as I turn it off and turn Windows Authentication back on, I get the 500 errors.

   When running under Anonymous Authentication, the site uses the application pool identity. When testing with the Windows Authentication, I have been using a user with global admin permissions. All other plugins work as expected, just not WP Super Cache.

   We need to keep the password protection on, and yet we must demo the Super Cache functionality to our management in dev and staging.

   Please advise!

   http://wordpress.org/extend/plugins/wp-super-cache/

2. ultradust
   Member
   Posted 4 months ago #

   To be specific: The plugin was throwing 500 errors when attempting to view/change settings, etc. It wasn't usable at all. I briefly turned off Windows Authentication and hit the pages again, and they worked (I assume that the various changes/files required were performed while authentication was off). However, when I turn authentication back on, I get 500 errors. For example, when trying to use the "Test Cache" feature, I get this:

   --------------------------------------------------------------
   HTTP Error 500.0 - Internal Server Error
   C:\PHP\php-cgi.exe - The FastCGI process exited unexpectedly
   Detailed Error Information
   Module FastCgiModule
   Notification ExecuteRequestHandler
   Handler PHP via FastCGI
   Error Code 0xc0000005
   Requested URL http://domain.com:80/wp-admin/options-general.php?page=wpsupercache&tab=easy
   Physical Path C:\inetpub\wwwroot\sites\domain\staging\wp-admin\options-general.php
   Logon Method Negotiate
   Logon User BC1\adminuser
   Most likely causes:
   IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
   IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
   IIS was not able to process configuration for the Web site or application.
   The authenticated user does not have permission to use this DLL.
   The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
   Things you can try:
   Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
   Check the event logs to see if any additional information was logged.
   Verify the permissions for the DLL.
   Install the .NET Extensibility feature if the request is mapped to a managed handler.
   Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
   Links and More Information
   This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
   View more information »

   Microsoft Knowledge Base Articles:

   294807
   --------------------------------------------------------------

   When I turn on error logging and PHP errors, nothing specific is provided via the error. I only get generic 500 errors.

3. ultradust
   Member
   Posted 4 months ago #

   OK, I spent quite a bit of time attempting to locate the cause of the errors. The server configuration has no known issues. It is set up properly for use with Windows Authentication and all other plugins and platforms (including Magento) work with no problems. In general, I am not seeing these 500 errors except when using the WP Super Cache plugin.

   I did a comprehensive test on various versions of PHP. Given the server configuration, here are the results:

   PHP 5.3.6 and older - WP Super Cache works as expected (except that the test results don't match) while using Windows Authentication.

   PHP 5.3.7 and newer - WP Super Cache fails with 500 errors while using Windows Authentication.

   It looks like something changed from underneath WP Super Cache in PHP to cause this major problem.

4. Donncha O Caoimh
   Member
   Posted 4 months ago #

   Ouch, I don't have a Windows server to test that but thank you for testing it so well. Hopefully if you're having issues then others are too and a fix will be forthcoming from PHP.

5. ultradust
   Member
   Posted 4 months ago #

   OK - I filed a bug report here:

   https://bugs.php.net/bug.php?id=60787

   However:

   * In all of my WordPress installations with various plugins, only your plugin is failing in this manner. Are you certain there isn't something about how the plugin is written that is causing the issue? (It looks like maybe the plugin is asking to run under a different account context than the rest.)

   * The plugin never really quite worked perfectly with Windows Authentication to begin with (the test files never match). Do you think there may be a fundamental problem, going even farther back, that needs to be addressed to make this plugin conform to the requirements needed for use with Windows Authentication? Again, other plugins manage to work fine with WA.

   Thanks for a really cool plugin and for your help in the community; I hope I can get it working.

6. Donncha O Caoimh
   Member
   Posted 4 months ago #

   I honestly don't know. Could it be because the plugin writes to wp-content/wp-cache-config.php when settings are updated? You could edit wp-cache.php and look for wp_cache_replace_line - make it "return true;" to disable writing.

   I have no experience with a Windows server so I can't say for sure.

7. ultradust
   Member
   Posted 4 months ago #

   OK, I'll try to test that.

   In the meantime, PHP is demanding a short script to demonstrate the error (see https://bugs.php.net/bug.php?id=60787). I don't know how to isolate this issue to a simple script as they ask. Do you have any recommendations?

8. ultradust
   Member
   Posted 4 months ago #

   PHP is not providing any help on this issue so far. Any thoughts on how to proceed?

Reply

You must log in to post.