aboutsummaryrefslogtreecommitdiff
path: root/content/post/2013-10-07-golang-http-handlers-as-middleware.markdown
diff options
context:
space:
mode:
Diffstat (limited to 'content/post/2013-10-07-golang-http-handlers-as-middleware.markdown')
-rw-r--r--content/post/2013-10-07-golang-http-handlers-as-middleware.markdown2
1 files changed, 2 insertions, 0 deletions
diff --git a/content/post/2013-10-07-golang-http-handlers-as-middleware.markdown b/content/post/2013-10-07-golang-http-handlers-as-middleware.markdown
index 812632c..5b9b652 100644
--- a/content/post/2013-10-07-golang-http-handlers-as-middleware.markdown
+++ b/content/post/2013-10-07-golang-http-handlers-as-middleware.markdown
@@ -8,6 +8,8 @@ tags: ["go", "http"]
Most modern web stacks allow the "filtering" of requests via stackable/composable middleware, allowing you to cleanly separate cross-cutting concerns from your web application. This weekend I needed to hook into go's ```http.FileServer``` and was pleasantly surprised how easy it was to do.
+<!--more-->
+
Let's start with a basic file server for ```/tmp```:
```go main.go