kong 3.3.0 build generates an error when the request is closed due to a timeout

[fantini]

A 504 error is expected, but returns a 500 error in the request. Example of the generated error:

2023/12/04 14:02:32 [error] 38#0: *9824 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.19.10.1, server: kong, request: "GET /intranet/celepar/apigateway/servico/v1/sleep/4000 HTTP/1.1", upstream: "https://10.15.96.163:443/gestaoapigateway-servicos/api/v1/suporte/sleep/4000", host: "kong.apps.ocp4.celepar.parana"

2023/12/04 14:02:32 [error] 38#0: *9824 failed to load inlined Lua code: rewrite_by_lua(nginx-kong.conf:289):1: unexpected symbol near ';', client: 172.19.10.1, server: kong, request: "GET /intranet/celepar/apigateway/servico/v1/sleep/4000 HTTP/1.1", upstream: "https://10.15.96.163:443/gestaoapigateway-servicos/api/v1/suporte/sleep/4000", host: "kong.apps.ocp4.celepar.parana"

For testing I used the following settings:

• kong.yml
• Dockerfile
• docker-entrypoint.sh
  kong.tar.gz

I also generated my own build with the scripts, but the same errors occurred in the tests run

Note: if I comment out lines 289 and 290 in the nginx_kong.lua file, the error did not occur and the request returns 504 as expected

[gerrith3]

@seth-priya I don't see Sumit in this repo - would it make sense to assign this to him?

[seth-priya]

@sumitd2 can you please check