10
95%
main: 95%

Ran 10 Jul 2024 04:28PM UTC

Files 43

Run time 8s

Badge

Embed ▾

Committed 10 Jul 2024 04:00PM UTC coverage: 89.859% (+0.02%) from 89.84%

Job # 9877542181.10

Build Type

push

github

Committed by

thibaultcha

Commit Message

fix(proxy-wasm) only inject shim headers after on_response_headers

Due to some Nginx internals (some response headers are added after our
module is executed but before the response is sent) we inject "shim
headers" into the `get_http_response_headers()` API. Some heuristics are
used to determine whether or not `Transfer-Encoding`, `Connection`, or
other "last minute" headers will be injected or not.

The issue is that the heuristics used are only valid during response
production and after (e.g. `r->chunked` or
`r->headers_out.content_length_n` may only be relevant during response
production). If a user uses `get_http_response_headers()` in request
phases, the returned headers may include elements that will not actually
be included in the response (e.g. `Transfer-Encoding`).

We now enforce that shim response headers should only be injected during
and after `on_http_response_headers`.

Run Details

7541 of 8392 relevant lines covered (89.86%)

12451.82 hits per line

Kong / ngx_wasm_module / 9877542181 / 10
95%
main: 95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job unit-ngx_1.27.0-wasmer-no_ipc-ssl-debug-no_hup-static - 9877542181.10

Kong / ngx_wasm_module / 9877542181 / 10 95% main: 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job unit-ngx_1.27.0-wasmer-no_ipc-ssl-debug-no_hup-static - 9877542181.10

Kong / ngx_wasm_module / 9877542181 / 10
95%
main: 95%

README BADGES
x