个人中心
gpt4 book ai didi

wordpress - 带有 wordpress 的 Varnish 破坏了 wordpress 可视化编辑器？

转载 作者：行者123 更新时间：2023-12-03 17:45:42 26 4
gpt4 key购买 nike

嗨，我对 Wordpress 3.5 Varnish 3.02 和 Ubuntu 有一个非常奇怪的问题，其中可视化编辑器已经消失。在 html/visual 之间切换的按钮已经消失，只显示 html 编辑器。该站点缓存正常，没有 javascript 错误，也没有 apache 日志中的错误。 Varnish 在 80 上监听，Apache 在 8080 上监听。除编辑器外，其他一切正常。
当我绕过 Varnish 时，编辑器开关按钮会出现并且工作正常。这是我到目前为止所做的没有成功的事情:
- 禁用所有插件
- 切换到默认主题
- 检查 Firebug 是否有任何 jquery 错误(无)
- 绕过 Varnish (一切正常)
- 清除 Varnish 缓存(不走运)
- 重新上传了所有默认的 wordpress 文件
- 切换到早期版本的 Wordpress (3.5)
你认为可能是什么问题？在这个问题上，我已经摸索了一个星期了。

视频文件

 backend default {
    .host = "x.x.x.x";
    .port = "8080";
 }


 sub vcl_recv {

  if (req.http.host ~ "mydomain.com") {
    set req.http.x-Redir-Url = "http://www.anotherdomain.com/specific_folder/";
    error 750 req.http.x-Redir-Url;
  }

 }

include "devicedetect.vcl";

# Called after a document has been successfully retrieved from the backend.
sub vcl_recv {
    call devicedetect;


    # Allow the back-end to serve up stale content if it is responding slowly.
    set req.grace = 2m;

    # Always cache the following file types for all users.
    if ( req.url ~ "(?i)\.(png|gif|jpeg|jpg|ico|swf|css|js|html|htm)(\?[a-z0-9]+)?$" ) {
            unset req.http.cookie;
    }

    # Don't serve cached pages to logged in users
    if ( req.http.cookie ~ "wordpress_logged_in" || req.url ~ "vaultpress=true" ) {
            return( pass );
    }

    # Drop any cookies sent to WordPress.
    if ( ! ( req.url ~ "wp-(login|admin)" ) ) {
            unset req.http.cookie;
    }

    # Handle compression correctly. Different browsers send different
    # "Accept-Encoding" headers, even though they mostly all support the same
    # compression mechanisms. By consolidating these compression headers into
    # a consistent format, we can reduce the size of the cache and get more hits.
    # @see: http://varnish.projects.linpro.no/wiki/FAQ/Compression
    if ( req.http.Accept-Encoding ) {

            if ( req.http.Accept-Encoding ~ "gzip" ) {
                    # If the browser supports it, we'll use gzip.
                    set req.http.Accept-Encoding = "gzip";
            }

            else if ( req.http.Accept-Encoding ~ "deflate" ) {
                    # Next, try deflate if it is supported.
                    sset req.http.Accept-Encoding = "deflate";
            }
            else {
                    # Unknown algorithm. Remove it and send unencoded.
                    unset req.http.Accept-Encoding;
            }

    }

}

# MOBILE AND UA DETECTION - override the header before it is sent to the backend
sub vcl_miss { if (req.http.X-UA-Device) { set bereq.http.User-Agent = req.http.X-UA-Device; } }
sub vcl_pass { if (req.http.X-UA-Device) { set bereq.http.User-Agent = req.http.X-UA-Device; } }


sub vcl_fetch {
    #SET UA BEFORE SENDING TO BACKEND
    if (req.http.X-UA-Device) {
            if (!beresp.http.Vary) { # no Vary at all
                    set beresp.http.Vary = "X-UA-Device";
            } elseif (beresp.http.Vary !~ "X-UA-Device") { # add to existing Vary
                    set beresp.http.Vary = beresp.http.Vary + ", X-UA-Device";
            }
    }
    set beresp.http.X-UA-Device = req.http.X-UA-Device;



    #Fix Login under wordpress
    if (beresp.http.set-cookie ~ "sessionid" || beresp.http.set-cookie ~ "csrftoken") {
    #       return (pass);
    } else {
            return (deliver);
    }

    set beresp.ttl = 20m;

    # Allow items to be stale if needed.
    set beresp.grace = 2m;

    # Drop any cookies WordPress tries to send back to the client.
    if ( ! req.url ~ "wp-(login|admin)" && ! req.http.cookie ~ "wordpress_logged_in" ) {
            unset beresp.http.set-cookie;
    }

}

sub vcl_error {
 #REDIRECTION
    if (obj.status == 750) {
            set obj.http.Location = obj.response;
            set obj.status = 301;
            return (deliver);
    }

set obj.http.Content-Type = "text/html; charset=utf-8";
set obj.http.Retry-After = "5";
synthetic {"
    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html>
    <head>
    <title>OOPS UNE ERREUR S'EST PRODUITE</title>
    <style src="css/style.css"></style>
    </head>
    <body>
    <h1>Oh! Oh! Nos excuses. Une erreure s'est produite. On s'en occupe.</h1>
    </body>
    </html>
"};
    return (deliver);
}

sub vcl_deliver {
  if ((req.http.X-UA-Device) && (resp.http.Vary)) {
    set resp.http.Vary = regsub(resp.http.Vary, "X-UA-Device", "User-Agent");
  }
}


**************THIS IS ANOTHER FILE(devicedetect.vcl)**********************

INCLUDED DEVICE DETECTION:

#
# detectdevice.vcl - regex based device detection for Varnish
# http://github.com/varnish/varnish-devicedetect/
#
# Author: Lasse Karstensen <lasse@varnish-software.com>

sub devicedetect {
    unset req.http.X-UA-Device;
    set req.http.X-UA-Device = "pc";

    # Handle that a cookie may override the detection alltogether.
    if (req.http.Cookie ~ "(?i)X-UA-Device-force") {
            /* ;?? means zero or one ;, non-greedy to match the first. */
            set req.http.X-UA-Device = regsub(req.http.Cookie, "(?i).*X-UA-Device-force=([^;]+);??.*", "\1");
            /* Clean up our mess in the cookie header */
            set req.http.Cookie = regsuball(req.http.Cookie, "(^|; ) *X-UA-Device-force=[^;]+;? *", "\1");
            /* If the cookie header is now empty, or just whitespace, unset it. */
            if (req.http.Cookie ~ "^ *$") { unset req.http.Cookie; }
    } else {
            if (req.http.User-Agent ~ "(?i)(ads|google|bing|msn|yandex|baidu|ro|career|)bot" ||
                req.http.User-Agent ~ "(?i)(baidu|jike|symantec)spider" ||
                req.http.User-Agent ~ "(?i)scanner" ||
                req.http.User-Agent ~ "(?i)(web)crawler") {
                    set req.http.X-UA-Device = "bot"; }
            elsif (req.http.User-Agent ~ "(?i)ipad")        { set req.http.X-UA-Device = "tablet-ipad"; }
            elsif (req.http.User-Agent ~ "(?i)ip(hone|od)") { set req.http.X-UA-Device = "mobile-iphone"; }
            /* how do we differ between an android phone and an android tablet?
               http://stackoverflow.com/questions/5341637/how-do-detect-android-tablets-in-general-useragent */
            elsif (req.http.User-Agent ~ "(?i)android.*(mobile|mini)") { set req.http.X-UA-Device = "mobile-android"; }
            // android 3/honeycomb was just about tablet-only, and any phones will probably handle a bigger page layout.
            elsif (req.http.User-Agent ~ "(?i)android 3")              { set req.http.X-UA-Device = "tablet-android"; }
            // May very well give false positives towards android tablets. Suggestions welcome.
            elsif (req.http.User-Agent ~ "(?i)android")         { set req.http.X-UA-Device = "tablet-android"; }
            elsif (req.http.User-Agent ~ "Mobile.+Firefox")     { set req.http.X-UA-Device = "mobile-firefoxos"; }
            elsif (req.http.User-Agent ~ "^HTC" ||
                req.http.User-Agent ~ "Fennec" ||
                req.http.User-Agent ~ "IEMobile" ||
                req.http.User-Agent ~ "BlackBerry" ||
                req.http.User-Agent ~ "SymbianOS.*AppleWebKit" ||
                req.http.User-Agent ~ "Opera Mobi") {
                    set req.http.X-UA-Device = "mobile-smartphone";
            }
            elsif (req.http.User-Agent ~ "(?i)symbian" ||
                req.http.User-Agent ~ "(?i)^sonyericsson" ||
                req.http.User-Agent ~ "(?i)^nokia" ||
                req.http.User-Agent ~ "(?i)^samsung" ||
                req.http.User-Agent ~ "(?i)^lg" ||
                req.http.User-Agent ~ "(?i)bada" ||
                req.http.User-Agent ~ "(?i)blazer" ||
                req.http.User-Agent ~ "(?i)cellphone" ||
                req.http.User-Agent ~ "(?i)iemobile" ||
                req.http.User-Agent ~ "(?i)midp-2.0" ||
                req.http.User-Agent ~ "(?i)u990" ||
                req.http.User-Agent ~ "(?i)netfront" ||
                req.http.User-Agent ~ "(?i)opera mini" ||
                req.http.User-Agent ~ "(?i)palm" ||
                req.http.User-Agent ~ "(?i)nintendo wii" ||
                req.http.User-Agent ~ "(?i)playstation portable" ||
                req.http.User-Agent ~ "(?i)portalmmm" ||
                req.http.User-Agent ~ "(?i)proxinet" ||
                req.http.User-Agent ~ "(?i)sonyericsson" ||
                req.http.User-Agent ~ "(?i)symbian" ||
                req.http.User-Agent ~ "(?i)windows\ ?ce" ||
                req.http.User-Agent ~ "(?i)winwap" ||
                req.http.User-Agent ~ "(?i)eudoraweb" ||
                req.http.User-Agent ~ "(?i)htc" ||
                req.http.User-Agent ~ "(?i)240x320" ||
                req.http.User-Agent ~ "(?i)avantgo") {
                    set req.http.X-UA-Device = "mobile-generic";
            }
    }

}

最佳答案

我在遇到同样问题时偶然发现了这个问题。我尝试按照提问者在后续“回复”中的建议进行操作，但我不走运。

问题中描述的问题源于这样一个事实，即 Wordpress 仅在用户代理与已知编辑器匹配时才启用 TinyMCE(视觉)编辑器。对于其他所有内容，默认情况下它将禁用它。结合 devicedetect.vcl ，您可能会看到这是怎么回事...

因此，因为我们将“pc”、“mobile-platform”等发送到后端(Wordpress)，它永远不会真正知道您正在使用的浏览器。

在我的 VCL 中，我使用以下代码完全禁用了/wp-admin 的缓存:

if (req.url ~ "/wp-(login|admin)") {
    return (pass);
}

当我实现 devicedetect.vcl我在我的 sub vcl_recv 顶部调用例程，因此用户代理已经以修改状态到达我的后端。

解决方法是 return (pass)在 /wp-(login|admin) 之前 你 call devicedetect ， 像这样: 
if (req.url ~ "/wp-(login|admin)") {
    return (pass);
}
call devicedetect;

关于wordpress - 带有 wordpress 的 Varnish 破坏了 wordpress 可视化编辑器？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/18286491/

26 4 0
文章推荐： nginx - Vagrant + Puppets 模块
文章推荐： sql - 将sqlite中不同表的数据从一列复制到另一列
文章推荐： sql - SQLite元组相等性比较
文章推荐： magento - 使用 Varnish -松节油组合排除结帐和客户模块/magento 部分
行者123
个人简介

我是一名优秀的程序员,十分优秀！

滴滴打车优惠券免费领取
滴滴打车优惠券
全站热门文章
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com