diff options
author | Matt Holt <mholt@users.noreply.github.com> | 2019-07-11 15:32:34 -0600 |
---|---|---|
committer | GitHub <noreply@github.com> | 2019-07-11 15:32:34 -0600 |
commit | 9343403358bd34b787a209b41c5b820781f78890 (patch) | |
tree | 559461c6504b7c1be38e0ddfbf0793b473ef8d66 /modules/caddyhttp/encode | |
parent | 6dfba5fda82e216cffb117a62fcefbe61cd25a34 (diff) |
Flatten HTTP handler config (#2662) (#2663)
Differentiating middleware and responders has one benefit, namely that
it's clear which module provides the response, but even then it's not
a great advantage. Linear handler config makes a little more sense,
giving greater flexibility and simplifying the core a bit, even though
it's slightly awkward that handlers which are responders may not use
the 'next' handler that is passed in at all.
Diffstat (limited to 'modules/caddyhttp/encode')
-rw-r--r-- | modules/caddyhttp/encode/encode.go | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/modules/caddyhttp/encode/encode.go b/modules/caddyhttp/encode/encode.go index 2b45917..c78ccb9 100644 --- a/modules/caddyhttp/encode/encode.go +++ b/modules/caddyhttp/encode/encode.go @@ -36,7 +36,7 @@ import ( func init() { caddy.RegisterModule(caddy.Module{ - Name: "http.middleware.encode", + Name: "http.handlers.encode", New: func() interface{} { return new(Encode) }, }) } |