Skip to content

Segmentation fault when instance traps after sending local response #696

@dev-null-undefined

Description

@dev-null-undefined

I believe there is a bug in the code where when you send a local response which overrides the action, and trap after it nginx will then segfault when trying to cleanup the request and the 503 response is not sent.

Probably issue here, I believe trapping should have higher priority then action
https://github.com/Kong/ngx_wasm_module/blob/main/src/common/proxy_wasm/ngx_proxy_wasm.c#L864-L890

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions