# Response phase skipped when HTTP/2 is in use

**URL:** <https://discuss.konghq.com/t/response-phase-skipped-when-http-2-is-in-use/10306>\
**Category:** General\
**Tags:** kong-gateway\
**Created:** [June 21, 2022, 9:35pm UTC](https://discuss.konghq.com/t/response-phase-skipped-when-http-2-is-in-use/10306 "2022-06-21T21:35:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Josh\_Kreitz](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/josh_kreitz/32/3491_2.png) [@Josh\_Kreitz](https://discuss.konghq.com/u/Josh_Kreitz)\
**Post date:** [June 21, 2022, 9:35pm UTC](https://discuss.konghq.com/t/response-phase-skipped-when-http-2-is-in-use/10306/1 "2022-06-21T21:35:18Z")

</div>

Hello, I’m developing an authentication plugin for Kong that utilizes both the access and response phases of the request lifecycle. Normally, on HTTP/1.1, both the request and response are validated by our plugin before being allowed to continue through Kong. When using HTTP/2.0 however, I see the following message logged in error.log:

2022/06/21 21:30:53 [notice] 195011#0: \*13744 [lua] init.lua:981: access(): response buffering was turned off: incompatible HTTP version (2), client: omitted, server: kong, request: “GET /? HTTP/2.0”, host: “omitted”

After this, the response phase of my plugin does not get called, but the response is allowed to continue to the client anyway. This effectively bypasses authentication on the server response! Is this intended? Is there a workaround for this, perhaps by disabling HTTP/2.0 communications through Kong?

---

<div class="post-metadata">

**Author:** ![fomm](https://avatars.discourse-cdn.com/v4/letter/f/ea666f/32.png) [@fomm](https://discuss.konghq.com/u/fomm)\
**Post date:** [June 22, 2022, 12:13am UTC](https://discuss.konghq.com/t/response-phase-skipped-when-http-2-is-in-use/10306/2 "2022-06-22T00:13:40Z")

</div>

This is documented [here](https://docs.konghq.com/gateway-oss/2.4.x/plugin-development/custom-logic/#available-contexts).

> If a module implements the `response` function, Kong Gateway (OSS) will automatically activate the “buffered proxy” mode, as if the [`kong.service.request.enable_buffering()` function](https://docs.konghq.com/gateway-oss/2.4.x/pdk/kong.service.request/#kongservicerequestenable_buffering) had been called. Because of a current Nginx limitation, this doesn’t work for HTTP/2 or gRPC upstreams.