unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 2/2] examples: add varnish-4.vcl
Date: Fri,  1 Jul 2016 15:42:23 +0000	[thread overview]
Message-ID: <20160701154223.3892-3-e@80x24.org> (raw)
In-Reply-To: <20160701154223.3892-1-e@80x24.org>

Well, I'm fumbling along with this config.  Might as well
fumble along with it publically :)
---
 examples/varnish-4.vcl | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 74 insertions(+)
 create mode 100644 examples/varnish-4.vcl

diff --git a/examples/varnish-4.vcl b/examples/varnish-4.vcl
new file mode 100644
index 0000000..7439679
--- /dev/null
+++ b/examples/varnish-4.vcl
@@ -0,0 +1,74 @@
+# Example VCL for Varnish 4.0 with public-inbox WWW code
+# This is based on what shipped for 3.x a long time ago (I think)
+# and I'm hardly an expert in VCL (nor should we expect anybody
+# who maintains a public-inbox HTTP interface to be).
+#
+# It seems to work for providing some protection from traffic
+# bursts; but perhaps the public-inbox WWW interface can someday
+# provide enough out-of-the-box performance that configuration
+# of an extra component is pointless.
+
+vcl 4.0;
+backend default {
+	.host = "127.0.0.1";
+	.port = "280";
+}
+
+sub vcl_recv {
+	if (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.method != "GET" &&
+			req.method != "HEAD" &&
+			req.method != "PUT" &&
+			req.method != "POST" &&
+			req.method != "TRACE" &&
+			req.method != "OPTIONS" &&
+			req.method != "DELETE") {
+		/* Non-RFC2616 or CONNECT which is weird. */
+		return (pipe);
+	}
+	if (req.method != "GET" && req.method != "HEAD") {
+		/* We only deal with GET and HEAD by default */
+		return (pass);
+	}
+	if (req.http.Authorization || req.http.Cookie) {
+		/* Not cacheable by default */
+		return (pass);
+	}
+	return (hash);
+}
+
+sub vcl_hash {
+	hash_data(req.url);
+	if (req.http.host) {
+		hash_data(req.http.host);
+	} else {
+		hash_data(server.ip);
+	}
+	if (req.http.X-Forwarded-Proto) {
+		hash_data(req.http.X-Forwarded-Proto);
+	}
+	return (lookup);
+}
+
+sub vcl_backend_response {
+	set beresp.grace = 60s;
+	set beresp.do_stream = true;
+	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;
+		set beresp.uncacheable = true;
+		return (deliver);
+	} else {
+		set beresp.ttl = 10s;
+	}
+	return (deliver);
+}
-- 
EW


      parent reply	other threads:[~2016-07-01 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-01 15:42 [PATCH 0/2] performance-related notes+docs Eric Wong
2016-07-01 15:42 ` [PATCH 1/2] TODO: update documentation for performance items Eric Wong
2016-07-01 15:42 ` Eric Wong [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160701154223.3892-3-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).