Brent Yarger

Should we also be setting realm and/or the error in the www-authenticate header? Example: ``` WWW-Authenticate: Bearer realm="example", error="invalid_token", error_description="The access token expired" ```

Is it possible to add a test for restarting kong with the cache enabled? Otherwise LGTM

> @brentos > > [765baba](https://github.com/Kong/kong/commit/765baba47d1f92d83094315a0e349880fdf08eed) adds an integration test for start/restart. There's not a lot we can inspect and assert upon without making sketchy assumptions about wasmtime's cache implementation, so...

Kong has a KB article about this, you need to increase the `client_body_buffer_size`: https://support.konghq.com/support/s/article/Kong-plugin-produces-a-warning-a-client-request-body-is-buffered-to-a-temporary-file

Kong runs on nginx, so that is why we are setting this nginx variable. You either set this in kong.conf: ```nginx_http_client_body_buffer_size``` Or as a Kong environment variable: ```KONG_NGINX_HTTP_CLIENT_BODY_BUFFER_SIZE```

@ram-appsentinels Could you share your JWT plugin config?

@ram-appsentinels I'm not able to reproduce this, can you provide all reproduction steps? Kong configuration, consumer creation, jwt creation, etc?

@flrgh it looks like this is failing for the build & test step. Does the new wasm32-wasip1 target move the files to a different directory? Maybe target/wasm32-wasip1?

That is a valid approach but there is no way to configure each instance properly, right? The "instanceAddress" needs to be populated with its LB address.

@hishamhm or @leafo let me know if this is on the right track. A couple tests fail due to this change, I'll update those and add them to this PR.