openresty / openresty/lua-resty-core
OpenResty fails with ERR_EMPTY_RESPONSE
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 852
- Forks
- 286
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
My OpenResty application is failing with a ERR_EMPTY_RESPONSE. There are no error logs in access/error at all. I'm using https://github.com/3scale/lua-resty-url and this is causing a failure.
I tracked down the error by commenting out the source and managed to see the problem is from https://github.com/3scale/lua-resty-url/blob/master/src/resty/url.lua#L48. In return, I tracked the bug down in resty.core and it is coming from https://github.com/openresty/lua-resty-core/blob/master/lib/resty/core/regex.lua#L170
So the ffi.C.ngx_http_lua_ffi_compile_regex is causing this ERR_EMPTY_RESPONSE.
I have tried removing and reinstalling OpenResty without any luck. Adding debug to log levels also doesn't provide any useful information.
Completely stuck as I can't even find any logs to understand what is broken.
Help is appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the call from src/resty/url.lua#L48 through lua-resty-core/lib/resty/core/regex.lua#L170, focusing on ffi.C.ngx_http_lua_ffi_compile_regex. The issue names no test or acceptance criterion, so completion would require an agreed diagnosis and a fix for the ERR_EMPTY_RESPONSE behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100