2019-08-10 02:05:47 +08:00
|
|
|
// Copyright 2015 Matthew Holt and The Caddy Authors
|
|
|
|
//
|
|
|
|
// Licensed under the Apache License, Version 2.0 (the "License");
|
|
|
|
// you may not use this file except in compliance with the License.
|
|
|
|
// You may obtain a copy of the License at
|
|
|
|
//
|
|
|
|
// http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
//
|
|
|
|
// Unless required by applicable law or agreed to in writing, software
|
|
|
|
// distributed under the License is distributed on an "AS IS" BASIS,
|
|
|
|
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
|
|
// See the License for the specific language governing permissions and
|
|
|
|
// limitations under the License.
|
|
|
|
|
|
|
|
package rewrite
|
|
|
|
|
|
|
|
import (
|
2019-12-13 06:46:13 +08:00
|
|
|
"strconv"
|
2020-01-23 00:36:05 +08:00
|
|
|
"strings"
|
2019-12-13 06:46:13 +08:00
|
|
|
|
2019-08-10 02:19:56 +08:00
|
|
|
"github.com/caddyserver/caddy/v2/caddyconfig/httpcaddyfile"
|
2019-08-22 00:46:35 +08:00
|
|
|
"github.com/caddyserver/caddy/v2/modules/caddyhttp"
|
2019-08-10 02:05:47 +08:00
|
|
|
)
|
|
|
|
|
2019-08-22 00:46:35 +08:00
|
|
|
func init() {
|
2019-12-13 06:46:13 +08:00
|
|
|
httpcaddyfile.RegisterHandlerDirective("rewrite", parseCaddyfileRewrite)
|
|
|
|
httpcaddyfile.RegisterHandlerDirective("strip_prefix", parseCaddyfileStripPrefix)
|
|
|
|
httpcaddyfile.RegisterHandlerDirective("strip_suffix", parseCaddyfileStripSuffix)
|
|
|
|
httpcaddyfile.RegisterHandlerDirective("uri_replace", parseCaddyfileURIReplace)
|
2019-08-22 00:46:35 +08:00
|
|
|
}
|
|
|
|
|
2019-12-13 06:46:13 +08:00
|
|
|
// parseCaddyfileRewrite sets up a basic rewrite handler from Caddyfile tokens. Syntax:
|
2019-08-10 02:05:47 +08:00
|
|
|
//
|
|
|
|
// rewrite [<matcher>] <to>
|
|
|
|
//
|
2020-01-12 04:47:42 +08:00
|
|
|
// Only URI components which are given in <to> will be set in the resulting URI.
|
|
|
|
// See the docs for the rewrite handler for more information.
|
2019-12-13 06:46:13 +08:00
|
|
|
func parseCaddyfileRewrite(h httpcaddyfile.Helper) (caddyhttp.MiddlewareHandler, error) {
|
2019-08-22 00:46:35 +08:00
|
|
|
var rewr Rewrite
|
|
|
|
for h.Next() {
|
2019-10-17 05:18:02 +08:00
|
|
|
if !h.NextArg() {
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
2019-08-22 00:46:35 +08:00
|
|
|
rewr.URI = h.Val()
|
2019-10-07 10:46:10 +08:00
|
|
|
if h.NextArg() {
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
2019-08-10 02:05:47 +08:00
|
|
|
}
|
2019-08-22 00:46:35 +08:00
|
|
|
return rewr, nil
|
2019-08-10 02:05:47 +08:00
|
|
|
}
|
2019-12-13 06:46:13 +08:00
|
|
|
|
|
|
|
// parseCaddyfileStripPrefix sets up a handler from Caddyfile tokens. Syntax:
|
|
|
|
//
|
|
|
|
// strip_prefix [<matcher>] <prefix>
|
|
|
|
//
|
http: Change routes to sequential matcher evaluation (#2967)
Previously, all matchers in a route would be evaluated before any
handlers were executed, and a composite route of the matching routes
would be created. This made rewrites especially tricky, since the only
way to defer later matchers' evaluation was to wrap them in a subroute,
or to invoke a "rehandle" which often caused bugs.
Instead, this new sequential design evaluates each route's matchers then
its handlers in lock-step; matcher-handlers-matcher-handlers...
If the first matching route consists of a rewrite, then the second route
will be evaluated against the rewritten request, rather than the original
one, and so on.
This should do away with any need for rehandling.
I've also taken this opportunity to avoid adding new values to the
request context in the handler chain, as this creates a copy of the
Request struct, which may possibly lead to bugs like it has in the past
(see PR #1542, PR #1481, and maybe issue #2463). We now add all the
expected context values in the top-level handler at the server, then
any new values can be added to the variable table via the VarsCtxKey
context key, or just the GetVar/SetVar functions. In particular, we are
using this facility to convey dial information in the reverse proxy.
Had to be careful in one place as the middleware compilation logic has
changed, and moved a bit. We no longer compile a middleware chain per-
request; instead, we can compile it at provision-time, and defer only the
evaluation of matchers to request-time, which should slightly improve
performance. Doing this, however, we take advantage of multiple function
closures, and we also changed the use of HandlerFunc (function pointer)
to Handler (interface)... this led to a situation where, if we aren't
careful, allows one request routed a certain way to permanently change
the "next" handler for all/most other requests! We avoid this by making
a copy of the interface value (which is a lightweight pointer copy) and
using exclusively that within our wrapped handlers. This way, the
original stack frame is preserved in a "read-only" fashion. The comments
in the code describe this phenomenon.
This may very well be a breaking change for some configurations, however
I do not expect it to impact many people. I will make it clear in the
release notes that this change has occurred.
2020-01-10 01:00:13 +08:00
|
|
|
// The request path will be stripped the given prefix.
|
2019-12-13 06:46:13 +08:00
|
|
|
func parseCaddyfileStripPrefix(h httpcaddyfile.Helper) (caddyhttp.MiddlewareHandler, error) {
|
|
|
|
var rewr Rewrite
|
|
|
|
for h.Next() {
|
|
|
|
if !h.NextArg() {
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
2020-01-12 04:47:42 +08:00
|
|
|
rewr.StripPathPrefix = h.Val()
|
2020-01-23 00:36:05 +08:00
|
|
|
if !strings.HasPrefix(rewr.StripPathPrefix, "/") {
|
|
|
|
rewr.StripPathPrefix = "/" + rewr.StripPathPrefix
|
|
|
|
}
|
2019-12-13 06:46:13 +08:00
|
|
|
if h.NextArg() {
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return rewr, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// parseCaddyfileStripSuffix sets up a handler from Caddyfile tokens. Syntax:
|
|
|
|
//
|
|
|
|
// strip_suffix [<matcher>] <suffix>
|
|
|
|
//
|
http: Change routes to sequential matcher evaluation (#2967)
Previously, all matchers in a route would be evaluated before any
handlers were executed, and a composite route of the matching routes
would be created. This made rewrites especially tricky, since the only
way to defer later matchers' evaluation was to wrap them in a subroute,
or to invoke a "rehandle" which often caused bugs.
Instead, this new sequential design evaluates each route's matchers then
its handlers in lock-step; matcher-handlers-matcher-handlers...
If the first matching route consists of a rewrite, then the second route
will be evaluated against the rewritten request, rather than the original
one, and so on.
This should do away with any need for rehandling.
I've also taken this opportunity to avoid adding new values to the
request context in the handler chain, as this creates a copy of the
Request struct, which may possibly lead to bugs like it has in the past
(see PR #1542, PR #1481, and maybe issue #2463). We now add all the
expected context values in the top-level handler at the server, then
any new values can be added to the variable table via the VarsCtxKey
context key, or just the GetVar/SetVar functions. In particular, we are
using this facility to convey dial information in the reverse proxy.
Had to be careful in one place as the middleware compilation logic has
changed, and moved a bit. We no longer compile a middleware chain per-
request; instead, we can compile it at provision-time, and defer only the
evaluation of matchers to request-time, which should slightly improve
performance. Doing this, however, we take advantage of multiple function
closures, and we also changed the use of HandlerFunc (function pointer)
to Handler (interface)... this led to a situation where, if we aren't
careful, allows one request routed a certain way to permanently change
the "next" handler for all/most other requests! We avoid this by making
a copy of the interface value (which is a lightweight pointer copy) and
using exclusively that within our wrapped handlers. This way, the
original stack frame is preserved in a "read-only" fashion. The comments
in the code describe this phenomenon.
This may very well be a breaking change for some configurations, however
I do not expect it to impact many people. I will make it clear in the
release notes that this change has occurred.
2020-01-10 01:00:13 +08:00
|
|
|
// The request path will be stripped the given suffix.
|
2019-12-13 06:46:13 +08:00
|
|
|
func parseCaddyfileStripSuffix(h httpcaddyfile.Helper) (caddyhttp.MiddlewareHandler, error) {
|
|
|
|
var rewr Rewrite
|
|
|
|
for h.Next() {
|
|
|
|
if !h.NextArg() {
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
2020-01-12 04:47:42 +08:00
|
|
|
rewr.StripPathSuffix = h.Val()
|
2019-12-13 06:46:13 +08:00
|
|
|
if h.NextArg() {
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return rewr, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// parseCaddyfileURIReplace sets up a handler from Caddyfile tokens. Syntax:
|
|
|
|
//
|
|
|
|
// uri_replace [<matcher>] <find> <replace> [<limit>]
|
|
|
|
//
|
|
|
|
// Substring replacements will be performed on the request URI up to the
|
|
|
|
// number specified by limit, if any (default = 0, or no limit).
|
|
|
|
func parseCaddyfileURIReplace(h httpcaddyfile.Helper) (caddyhttp.MiddlewareHandler, error) {
|
|
|
|
var rewr Rewrite
|
|
|
|
|
|
|
|
var repls []replacer
|
|
|
|
|
|
|
|
for h.Next() {
|
|
|
|
args := h.RemainingArgs()
|
|
|
|
var find, replace, lim string
|
|
|
|
switch len(args) {
|
|
|
|
case 3:
|
|
|
|
lim = args[2]
|
|
|
|
fallthrough
|
|
|
|
case 2:
|
|
|
|
find = args[0]
|
|
|
|
replace = args[1]
|
|
|
|
default:
|
|
|
|
return nil, h.ArgErr()
|
|
|
|
}
|
|
|
|
|
|
|
|
var limInt int
|
|
|
|
if lim != "" {
|
|
|
|
var err error
|
|
|
|
limInt, err = strconv.Atoi(lim)
|
|
|
|
if err != nil {
|
|
|
|
return nil, h.Errf("limit must be an integer; invalid: %v", err)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
repls = append(repls, replacer{
|
|
|
|
Find: find,
|
|
|
|
Replace: replace,
|
|
|
|
Limit: limInt,
|
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
rewr.URISubstring = repls
|
|
|
|
|
|
|
|
return rewr, nil
|
|
|
|
}
|