• Vue SSR 报警 The client-side rendered virtual DOM tree is not matching server-rendered con


    接手前人留下来的 vue server side rendering 官网项目,访问测服路径时控制台报警

    [Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside <p>, or missing <tbody>. Bailing hydration and performing full client-side render.
    

    而官网的 SSR 渲染是根据进来的 hostname 是哪个而决定渲染哪个页面。出了的这个问题意味着 SSR 服务端渲染的页面内容,和前端客户端渲染时页面不一致。

    我在 node render 的部分打印返回

    const render = (req, res) => {
      // ......
      console.log('~~打印了~~~origin: ', origin, ' hostname: ' + req.hostname, ' host: ' + req.host)
      renderer.renderToString(context, (err, html) => {
        // ......
      })
    }
    

    访问 mctalk-test.netease.im 得到的是

    ~~打印了~~~origin:  http://mctalk-test.netease.im  hostname: home.netease.im  host: home.netease.im
    

    震惊,居然 origin 和 hostname 不一样。肯定是 nginx 转发过来的锅了,我找到 nginx 配置

    server {
      server_name home.netease.im mctalk-test.netease.im;
    
      listen 80;
    
      proxy_set_header X-Forwarded-For  $remote_addr;
      proxy_set_header X-Real-IP  $remote_addr;
      proxy_set_header X-Forwarded-Host $server_name;
      proxy_set_header Host $host;
      proxy_set_header X-Request-Host $host;
    
    
      location / {
        # ... 跳转配置略
      }
    }
    

    绕了两圈我才回过神,大概就是上文的 $host 变量出了问题搞得。

    所以把 nginx 配置拆开就更解决了

    server {
      server_name home.netease.im;
    
      listen 80;
    
      proxy_set_header X-Forwarded-For  $remote_addr;
      proxy_set_header X-Real-IP  $remote_addr;
      proxy_set_header X-Forwarded-Host $server_name;
      proxy_set_header Host $host;
      proxy_set_header X-Request-Host $host;
    
    
      location / {
        # ... 跳转配置略
      }
    }
    server {
      server_name mctalk-test.netease.im;
    
      listen 80;
    
      proxy_set_header X-Forwarded-For  $remote_addr;
      proxy_set_header X-Real-IP  $remote_addr;
      proxy_set_header X-Forwarded-Host $server_name;
      proxy_set_header Host $host;
      proxy_set_header X-Request-Host $host;
    
    
      location / {
        # ... 跳转配置略
      }
    }
    

    重启 nginx 后再次访问 mctalk-test.netease.im 得到的是

    ~~打印了~~~origin:  http://mctalk-test.netease.im  hostname: mctalk-test.netease.im  host: mctalk-test.netease.im
    

    渲染也正确了。

  • 相关阅读:
    SpringBoot整合Shiro实现基于角色的权限访问控制(RBAC)系统简单设计从零搭建
    Spring Cloud Feign 总结
    Spring Cloud Eureka 总结
    基于Shiro,JWT实现微信小程序登录完整例子
    解决JPA懒加载典型的N+1问题-注解@NamedEntityGraph
    一个微服务+DDD(领域驱动设计)的代码结构示例
    造轮子-AgileConfig基于.NetCore的一个轻量级配置中心
    ASP.NET Core Blazor 初探之 Blazor WebAssembly
    .Net Core
    AServer
  • 原文地址:https://www.cnblogs.com/everlose/p/14510550.html
Copyright © 2020-2023  润新知