dstein64

Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Forum: Plugins
    In reply to: [W3 Total Cache] Compatibility with WordPress Behind a Reverse Proxy
    Thread Starter dstein64

    (@dstein64)

    13 years, 3 months ago

    Two mistakes in my last post:

    I meant 404 error, not a 400 error. This was returned from nginx.

    Here is the code block (does not include back slashes):

    if ($request_uri !~ ^/blog/) {
   set $w3tc_rewrite 0;
}

    Forum: Plugins
    In reply to: [W3 Total Cache] Compatibility with WordPress Behind a Reverse Proxy
    Thread Starter dstein64

    (@dstein64)

    13 years, 3 months ago

    The latest update (0.9.2.7) made my blog start working again, even with “Disk: Enhanced” caching and the updated nginx rules. However, my homepage, still returned a 400 error. My blog is served from the /blog/ subdirectory of my site, and my homepage is served from /.

    It appeared that the W3TC nginx rules were applying a rewrite, so I added the following, which fixed my problem:

    if ($request_uri !~ ^\/blog\/) {
   set $w3tc_rewrite 0;
}

    Anyhow, the proxy issues are seemingly resolved, so I am marking this topic as resolved. Thanks.

    I suppose that my new issue is separate, or possibly a feature request if W3TC “Disk: Enhanced” caching doesn’t support blogs hosted from a subdirectory.

    Forum: Plugins
    In reply to: [W3 Total Cache] Compatibility with WordPress Behind a Reverse Proxy
    Thread Starter dstein64

    (@dstein64)

    13 years, 3 months ago

    I updated to the latest version. Upon updating, I received http errors (404 and 500 I think) when visiting my site. My nginx config was updated correctly.

    However, after deleting the W3 Total Cache nginx rules and switching from “Disk: Enhanced” to “Disk: Basic” page cache method, everything worked fine. Accessing my site via https, which is proxy passed to http, worked fine.

    I am not sure exactly what the initial problem was, but it may have to do with other settings in my nginx config. I’d be glad to look further into the problem if you’re interested, but I imagine it was specific to me, and is not causing any problem since “Disk: Basic” is giving me similar performance to what I had before the update.

Viewing 3 replies - 1 through 3 (of 3 total)