Varnish+Nginx 配置----Varnish

2024-03-31 12:38
文章标签 配置 nginx varnish

本文主要是介绍Varnish+Nginx 配置----Varnish,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

最近项目引入反向代理和缓存,熟悉了一下Squid、Apache、Valish、Nginx,根据项目实际进行选择,客观来说,采用Linux系统部署最好,也没有什么难度,但实际情况必须采用Windows系统(本着方案要结合现实的原则,研究要以Windows平台为主)。


一  Varnish启动:

e:
cd e:\varnish\bin
set PATH=%CD%;%PATH%
varnishd -a :7575 -T :11212 -f /etc/varnish_cst_cfg.vcl -s file,E:/var/varnish/tg/cache/jjtg,1024M -p thread_pool_max=5000 -p thread_pool_min=100 
REM pause
二  Varnish配置:
# This is a basic VCL configuration file for varnish.  See the vcl(7)
# man page for details on VCL syntax and semantics.
# 
# Default backend definition.  Set this to point to your content
# server.backend tgweb {.host = "192.168.45.45";.port = "7574";.connect_timeout = 20s;.first_byte_timeout = 20s;.between_bytes_timeout = 20s;}#允许刷新缓存的规则
#acl purgeAllow {
#     #只能本机进行刷新
#     "localhost";
#}# Below is a commented-out copy of the default VCL logic.  If you
# redefine any of these subroutines, the built-in logic will be
# appended to your code.sub vcl_recv {#判断请求主机,跳转到相应后端服务器if(req.http.host ~ "^(.*)(tg.stockjyb.com:7575)"){set req.backend=tgweb;}else{error 408 "Hostname not found"; }#grace缓存过期仍存放# 若backend是健康的,则仅grace 5s,如果backend不健康,则grace 1m。# 这里,5s的目的是为了提高高并发时的吞吐率;# 1m的目的是,backend挂了之后,还能继续服务一段时间,期望backend挂的不要太久。。。if (req.backend.healthy) {set req.grace = 5s;} else {set req.grace = 1m;}#刷新缓存的处理#if (req.request == "PURGE"){#    if(!client.ip ~ purgeAllow) {#            error 405 "Not allowed.";#    }#    #转到hit或者miss处理#    return (lookup);#}#移除一些特定格式的cookieif (req.url ~ "^(.*)\.(jpg|png|gif|jpeg|flv|bmp|gz|tgz|bz2|tbz|js|css|html|htm)($|\?)" ) {#移除cookie,以便能缓存到varnishunset req.http.cookie;}#Accept-Encoding 是浏览器发给服务器,声明浏览器支持的编码类型的#修正客户端的Accept-Encoding头信息#防止个别浏览器发送类似 deflate, gzipif (req.http.Accept-Encoding) {if (req.url ~ "^(.*)\.(jpg|png|gif|jpeg|flv|bmp|gz|tgz|bz2|tbz)($|\?)" ) {remove req.http.Accept-Encoding;}else if (req.http.Accept-Encoding ~ "gzip"){set req.http.Accept-Encoding = "gzip";} else if (req.http.Accept-Encoding ~ "deflate"){set req.http.Accept-Encoding = "deflate";} else if (req.http.Accept-Encoding ~ "sdch"){#chrome新增加的压缩set req.http.Accept-Encoding = "sdch";}else {remove req.http.Accept-Encoding;}}#首次访问增加X-Forwarded-For头信息,方便后端程序获取客户端ipif (req.restarts == 0) {if (req.http.x-forwarded-for) {set req.http.X-Forwarded-For =req.http.X-Forwarded-For + ", " + client.ip;} else {set req.http.X-Forwarded-For = client.ip;}}#if (req.request != "GET" &&#    req.request != "HEAD" &&#    req.request != "PUT" &&#    req.request != "POST" &&#    req.request != "TRACE" &&#    req.request != "OPTIONS" &&#    req.request != "DELETE") {#    /* Non-RFC2616 or CONNECT which is weird. */#    return (pipe);#}if (req.request != "GET" && req.request != "HEAD") {/* We only deal with GET and HEAD by default */return (pass);}if (req.http.Authorization) {/* Not cacheable by default */return (pass);}#js,css文件都有Cookie,不能每次都去后台服务器去取#if (req.http.Cookie) {#    /* Not cacheable by default */#    return (pass);#}#如果请求的是动态页面直接转发到后端服务器if (req.url ~ "^(.*)\.(aspx|asmx|ashx)($|.*)") {return (pass);}return (lookup);}sub vcl_pipe {# Note that only the first request to the backend will have# X-Forwarded-For set.  If you use X-Forwarded-For and want to# have it set for all requests, make sure to have:# set bereq.http.connection = "close";# here.  It is not set by default as it might break some broken web# applications, like IIS with NTLM authentication.return (pipe);}#放过,让其直接去后台服务器请求数据sub vcl_pass {return (pass);}sub vcl_hash {hash_data(req.url);if (req.http.host) {hash_data(req.http.host);} else {hash_data(server.ip);}#支持压缩的要增加,防止发送给不支持压缩的浏览器压缩的内容if(req.http.Accept-Encoding){hash_data(req.http.Accept-Encoding);}return (hash);}#缓存服务器lookup查找命中:hitsub vcl_hit {#刷新缓存的请求操作,设置TTL为0,返回处理结果代码#if (req.request == "PURGE") {#     set obj.ttl = 0s;#     error 200 "Purged.";# }//#缓存服务器命中后(查找到了)return (deliver);}#缓存服务器lookup查找没有命中:misssub vcl_miss {#刷新缓存的请求操作,#if (req.request == "PURGE") {#    error 404 "Not in cache.";#}//#缓存服务器没有命中(去后台服务器取)return (fetch);}#从后台服务器取回数据后,视情况是否进行缓存sub vcl_fetch {#如果请求的是动态页面直接发转发#动态请求回来的,一定要放在前面处理if (req.url ~ "^(.*)\.(aspx|asmx|ashx)($|.*)") {set beresp.http.Cache-Control="no-cache, no-store";unset beresp.http.Expires;return (deliver);}# 仅当该请求可以缓存时,才设置beresp.grace,若该请求不能被缓存,则不设置beresp.graceif (beresp.ttl > 0s) {set beresp.grace = 1m;}  if (beresp.ttl <= 0s ||beresp.http.Set-Cookie ||beresp.http.Vary == "*") {/** Mark as "Hit-For-Pass" for the next 2 minutes*/set beresp.ttl = 120 s;#下次请求时不进行lookup,直接passreturn (hit_for_pass);}#设置从后台服务器获得的特定格式文件的缓存TTLif (req.url ~ "^(.*)\.(pdf|xls|ppt|doc|docx|xlsx|pptx|chm|rar|zip)($|\?)")     {#移除服务器发送的cookie unset beresp.http.Set-Cookie;#加上缓存时间set beresp.ttl = 30d;return (deliver);}else if(req.url ~ "^(.*)\.(bmp|jpeg|jpg|png|gif|svg|png|ico|txt|css|js|html|htm)($|\?)"){#移除服务器发送的cookie unset beresp.http.Set-Cookie;#加上缓存时间set beresp.ttl = 15d;return (deliver);}else if(req.url ~ "^(.*)\.(mp3|wma|mp4|rmvb|ogg|mov|avi|wmv|mpeg|mpg|dat|3pg|swf|flv|asf)($|\?)"){#移除服务器发送的cookie unset beresp.http.Set-Cookie;#加上缓存时间set beresp.ttl = 30d;return (deliver);}#从后台服务器返回的response信息中,没有缓存的,不缓存if (beresp.http.Pragma ~"no-cache" || beresp.http.Cache-Control ~"no-cache" || beresp.http.Cache-Control ~"private") {return (deliver);}return (deliver);}#缓存服务器发送到客户端前调用sub vcl_deliver {#下面是添加一个Header标识,以判断缓存是否命中。if (obj.hits > 0) {set resp.http.X-Cache = "HIT from TG.varnish-cache.jjcj.com";#set resp.http.X-Varnish = "HIT from TG.varnish-cache.jjcj.com";} else {set resp.http.X-Cache = "MISS from TG.varnish-cache.jjcj.com";#set resp.http.X-Varnish = "MISS from TG.varnish-cache.jjcj.com";}#去掉不是必须的headerunset resp.http.Vary;unset resp.http.X-Powered-By;unset resp.http.X-AspNet-Version;return (deliver);}sub vcl_error {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>"} + obj.status + " " + obj.response + {"</title></head><body><h1>Error "} + obj.status + " " + obj.response + {"</h1><p>"} + obj.response + {"</p><h3>Guru Meditation:</h3><p>XID: "} + req.xid + {"</p><hr><p>Varnish cache server</p></body></html>"};return (deliver);}sub vcl_init {return (ok);}sub vcl_fini {return (ok);}

这篇关于Varnish+Nginx 配置----Varnish的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/864358

相关文章

QT Creator配置Kit的实现示例

《QTCreator配置Kit的实现示例》本文主要介绍了使用Qt5.12.12与VS2022时,因MSVC编译器版本不匹配及WindowsSDK缺失导致配置错误的问题解决,感兴趣的可以了解一下... 目录0、背景:qt5.12.12+vs2022一、症状:二、原因:(可以跳过,直奔后面的解决方法)三、解决方

SpringBoot路径映射配置的实现步骤

《SpringBoot路径映射配置的实现步骤》本文介绍了如何在SpringBoot项目中配置路径映射,使得除static目录外的资源可被访问,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一... 目录SpringBoot路径映射补:springboot 配置虚拟路径映射 @RequestMapp

Web服务器-Nginx-高并发问题

《Web服务器-Nginx-高并发问题》Nginx通过事件驱动、I/O多路复用和异步非阻塞技术高效处理高并发,结合动静分离和限流策略,提升性能与稳定性... 目录前言一、架构1. 原生多进程架构2. 事件驱动模型3. IO多路复用4. 异步非阻塞 I/O5. Nginx高并发配置实战二、动静分离1. 职责2

Nginx中配置使用非默认80端口进行服务的完整指南

《Nginx中配置使用非默认80端口进行服务的完整指南》在实际生产环境中,我们经常需要将Nginx配置在其他端口上运行,本文将详细介绍如何在Nginx中配置使用非默认端口进行服务,希望对大家有所帮助... 目录一、为什么需要使用非默认端口二、配置Nginx使用非默认端口的基本方法2.1 修改listen指令

解决Nginx启动报错Job for nginx.service failed because the control process exited with error code问题

《解决Nginx启动报错Jobfornginx.servicefailedbecausethecontrolprocessexitedwitherrorcode问题》Nginx启... 目录一、报错如下二、解决原因三、解决方式总结一、报错如下Job for nginx.service failed bec

Nginx添加内置模块过程

《Nginx添加内置模块过程》文章指导如何检查并添加Nginx的with-http_gzip_static模块:确认该模块未默认安装后,需下载同版本源码重新编译,备份替换原有二进制文件,最后重启服务验... 目录1、查看Nginx已编辑的模块2、Nginx官网查看内置模块3、停止Nginx服务4、Nginx

mysql5.7.15winx64配置全过程

《mysql5.7.15winx64配置全过程》文章详细介绍了MySQL5.7.15免安装版的配置步骤,包括解压安装包、设置环境变量、修改配置文件、初始化数据目录、安装服务、启动数据库、登录及密码修改... 目录前言一、首先下载安装包二、安android装步骤1.第一步解压文件2.配置环境变量3.复制my-

Jenkins的安装与简单配置过程

《Jenkins的安装与简单配置过程》本文简述Jenkins在CentOS7.3上安装流程,包括Java环境配置、RPM包安装、修改JENKINS_HOME路径及权限、启动服务、插件安装与系统管理设置... 目录www.chinasem.cnJenkins安装访问并配置JenkinsJenkins配置邮件通知

Conda国内镜像源及配置过程

《Conda国内镜像源及配置过程》文章介绍Conda镜像源使用方法,涵盖临时指定单个/多个源、永久配置及恢复默认设置,同时说明main(官方稳定)、free(逐渐弃用)、conda-forge(社区更... 目录一、Conda国内镜像源二、Conda临时使用镜像源指定单个源临时指定多个源创建环境时临时指定源

MySQL配置多主复制的实现步骤

《MySQL配置多主复制的实现步骤》多主复制是一种允许多个MySQL服务器同时接受写操作的复制方式,本文就来介绍一下MySQL配置多主复制的实现步骤,具有一定的参考价值,感兴趣的可以了解一下... 目录1. 环境准备2. 配置每台服务器2.1 修改每台服务器的配置文件3. 安装和配置插件4. 启动组复制4.