proxy: restrict functions for lua config vs route

Also changes the way the global context and thread contexts are fetched
from lua; via the VM extra space instead of upvalues, which is a little
faster and more universal.

It was always erroneous to run a lot of the config functions from routes
and vice versa, but there was no consistent strictness so users could
get into trouble.

1 files changed, 1 insertions, 0 deletions

diff --git a/proto_proxy.c b/proto_proxy.c
index 3bcaf9c..952c897 100644
--- a/proto_proxy.c
+++ b/proto_proxy.c
@@ -166,6 +166,7 @@ void proxy_thread_init(void *ctx, LIBEVENT_THREAD *thr) {
         fprintf(stderr, "Failed to allocate proxy thread stats\n");
         exit(EXIT_FAILURE);
     }
+    thr->proxy_ctx = ctx;
 
     // Initialize the lua state.
     lua_State *L = luaL_newstate();