2019-10-10 12:02:16 -05:00
|
|
|
package starlarkmw
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
|
|
|
"fmt"
|
|
|
|
"net/http"
|
|
|
|
|
|
|
|
"github.com/caddyserver/caddy/v2"
|
|
|
|
"github.com/caddyserver/caddy/v2/modules/caddyhttp"
|
|
|
|
"github.com/caddyserver/caddy/v2/modules/caddyhttp/starlarkmw/internal/lib"
|
2019-12-10 15:36:46 -05:00
|
|
|
caddyscript "github.com/caddyserver/caddy/v2/pkg/caddyscript/lib"
|
2019-10-10 12:02:16 -05:00
|
|
|
"github.com/starlight-go/starlight/convert"
|
|
|
|
"go.starlark.net/starlark"
|
|
|
|
)
|
|
|
|
|
|
|
|
func init() {
|
|
|
|
caddy.RegisterModule(StarlarkMW{})
|
|
|
|
}
|
|
|
|
|
|
|
|
// StarlarkMW represents a middleware responder written in starlark
|
|
|
|
type StarlarkMW struct {
|
|
|
|
Script string `json:"script"`
|
|
|
|
serveHTTP *starlark.Function
|
|
|
|
setup *starlark.Function
|
|
|
|
thread *starlark.Thread
|
|
|
|
loadMiddleware *lib.LoadMiddleware
|
|
|
|
execute *lib.Execute
|
|
|
|
globals *starlark.StringDict
|
|
|
|
gctx caddy.Context
|
|
|
|
rctx caddy.Context
|
|
|
|
rcancel context.CancelFunc
|
|
|
|
}
|
|
|
|
|
|
|
|
// CaddyModule returns the Caddy module information.
|
|
|
|
func (StarlarkMW) CaddyModule() caddy.ModuleInfo {
|
|
|
|
return caddy.ModuleInfo{
|
2019-12-10 15:36:46 -05:00
|
|
|
ID: "http.handlers.starlark",
|
|
|
|
New: func() caddy.Module { return new(StarlarkMW) },
|
2019-10-10 12:02:16 -05:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// ServeHTTP responds to an http request with starlark.
|
|
|
|
func (s *StarlarkMW) ServeHTTP(w http.ResponseWriter, r *http.Request) error {
|
|
|
|
var mwcancel context.CancelFunc
|
|
|
|
var mwctx caddy.Context
|
|
|
|
|
|
|
|
// call setup() to prepare the middleware chain if it is defined
|
|
|
|
if s.setup != nil {
|
|
|
|
mwctx, mwcancel = caddy.NewContext(s.gctx)
|
|
|
|
defer mwcancel()
|
|
|
|
|
|
|
|
s.loadMiddleware.Ctx = mwctx
|
|
|
|
args := starlark.Tuple{caddyscript.HTTPRequest{Req: r}}
|
|
|
|
|
|
|
|
_, err := starlark.Call(new(starlark.Thread), s.setup, args, nil)
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Errorf("starlark setup(), %v", err)
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// dynamically build middleware chain for each request
|
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-09 12:00:13 -05:00
|
|
|
var stack caddyhttp.Handler = caddyhttp.HandlerFunc(func(w http.ResponseWriter, r *http.Request) error {
|
2019-10-10 12:02:16 -05:00
|
|
|
wr, err := convert.ToValue(w)
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Errorf("cannot convert response writer to starlark value")
|
|
|
|
}
|
|
|
|
|
|
|
|
args := starlark.Tuple{wr, caddyscript.HTTPRequest{Req: r}}
|
|
|
|
v, err := starlark.Call(new(starlark.Thread), s.serveHTTP, args, nil)
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Errorf("starlark serveHTTP(), %v", err)
|
|
|
|
}
|
|
|
|
|
|
|
|
// if a responder type was returned from starlark we should run it otherwise it
|
|
|
|
// is expected to handle the request
|
|
|
|
if resp, ok := v.(lib.ResponderModule); ok {
|
|
|
|
return resp.Instance.ServeHTTP(w, r)
|
|
|
|
}
|
|
|
|
|
|
|
|
return nil
|
|
|
|
})
|
|
|
|
|
|
|
|
// TODO :- make middlewareResponseWriter exported and wrap w with that
|
|
|
|
var mid []caddyhttp.Middleware
|
|
|
|
for _, m := range s.execute.Modules {
|
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-09 12:00:13 -05:00
|
|
|
mid = append(mid, func(next caddyhttp.Handler) caddyhttp.Handler {
|
|
|
|
return caddyhttp.HandlerFunc(func(w http.ResponseWriter, r *http.Request) error {
|
2019-10-10 12:02:16 -05:00
|
|
|
return m.Instance.ServeHTTP(w, r, next)
|
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-09 12:00:13 -05:00
|
|
|
})
|
2019-10-10 12:02:16 -05:00
|
|
|
})
|
|
|
|
}
|
|
|
|
|
|
|
|
for i := len(mid) - 1; i >= 0; i-- {
|
|
|
|
stack = mid[i](stack)
|
|
|
|
}
|
|
|
|
|
|
|
|
s.execute.Modules = nil
|
|
|
|
|
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-09 12:00:13 -05:00
|
|
|
return stack.ServeHTTP(w, r)
|
2019-10-10 12:02:16 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
// Cleanup cleans up any modules loaded during the creation of a starlark route.
|
|
|
|
func (s *StarlarkMW) Cleanup() error {
|
|
|
|
s.rcancel()
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// Provision sets up the starlark env.
|
|
|
|
func (s *StarlarkMW) Provision(ctx caddy.Context) error {
|
|
|
|
// store global context
|
|
|
|
s.gctx = ctx
|
|
|
|
|
|
|
|
// setup context for cleaning up any modules loaded during starlark script parsing phase
|
|
|
|
rctx, cancel := caddy.NewContext(ctx)
|
|
|
|
s.rcancel = cancel
|
|
|
|
|
|
|
|
// setup starlark global env
|
|
|
|
env := make(starlark.StringDict)
|
|
|
|
loadMiddleware := lib.LoadMiddleware{}
|
|
|
|
loadResponder := lib.LoadResponder{
|
|
|
|
Ctx: rctx,
|
|
|
|
}
|
|
|
|
execute := lib.Execute{}
|
|
|
|
|
|
|
|
lr := starlark.NewBuiltin("loadResponder", loadResponder.Run)
|
|
|
|
lr = lr.BindReceiver(&loadResponder)
|
|
|
|
env["loadResponder"] = lr
|
|
|
|
|
|
|
|
lm := starlark.NewBuiltin("loadMiddleware", loadMiddleware.Run)
|
|
|
|
lm = lm.BindReceiver(&loadMiddleware)
|
|
|
|
env["loadMiddleware"] = lm
|
|
|
|
|
|
|
|
ex := starlark.NewBuiltin("execute", execute.Run)
|
|
|
|
ex = ex.BindReceiver(&execute)
|
|
|
|
env["execute"] = ex
|
|
|
|
|
|
|
|
// import caddyscript lib
|
|
|
|
env["time"] = caddyscript.Time{}
|
|
|
|
env["regexp"] = caddyscript.Regexp{}
|
|
|
|
|
|
|
|
// configure starlark
|
|
|
|
thread := new(starlark.Thread)
|
|
|
|
s.thread = thread
|
|
|
|
|
|
|
|
// run starlark script
|
|
|
|
globals, err := starlark.ExecFile(thread, "", s.Script, env)
|
|
|
|
if err != nil {
|
|
|
|
return fmt.Errorf("starlark exec file: %v", err.Error())
|
|
|
|
}
|
|
|
|
|
|
|
|
// extract defined methods to setup middleware chain and responder, setup is not required
|
|
|
|
var setup *starlark.Function
|
|
|
|
if _, ok := globals["setup"]; ok {
|
|
|
|
setup, ok = globals["setup"].(*starlark.Function)
|
|
|
|
if !ok {
|
|
|
|
return fmt.Errorf("setup function not defined in starlark script")
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
serveHTTP, ok := globals["serveHTTP"].(*starlark.Function)
|
|
|
|
if !ok {
|
|
|
|
return fmt.Errorf("serveHTTP function not defined in starlark script")
|
|
|
|
}
|
|
|
|
|
|
|
|
s.setup = setup
|
|
|
|
s.serveHTTP = serveHTTP
|
|
|
|
s.loadMiddleware = &loadMiddleware
|
|
|
|
s.execute = &execute
|
|
|
|
s.globals = &globals
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|