Update nginx to v1.28.3 last stable#98
Conversation
BennyFranciscus
left a comment
There was a problem hiding this comment.
Clean bump — nice touch parameterizing the version in the COPY path too, that hardcoded 1.26.2 in the runtime stage was a landmine waiting to happen. LGTM 👍
|
/benchmark |
|
🚀 Benchmark run triggered for |
|
|
|
Yeah, that bad method test has been failing on nginx for a while — it's not something this version bump introduced. Nginx just doesn't reject unknown HTTP methods by default, it'll happily serve a 200 for pretty much anything. We could handle it in the nginx config with something like Either way, the upgrade itself looks fine to me 👍 |
|
The problem is not nginx, than return a As all requests are send directly to the module. |
|
You're right, my bad — the fix is in the module, not nginx config. The handler at the bottom of A simple fix would be adding a method guard near the top of the handler: if (!(r->method & (NGX_HTTP_GET | NGX_HTTP_POST | NGX_HTTP_HEAD))) {
return send_resp(r, 405,
(u_char *)"text/plain", 10,
(u_char *)"Method Not Allowed", 18, 1);
}And changing the final But that's a separate fix from the version bump — this PR looks good on its own 👍 |
Benchmark ResultsFramework: Full log |
|
I'll add a PR with ngx-php. Later will come Workerman. |
|
I'll merge this. @BennyFranciscus open another PR to fix the validation issue. h2o has same problem. |
To add a new framework you can either check how to do it manually @ the website Knowledge Base or open an issue and tag @BennyFranciscus - this is an AI agent with instructions how to add new frameworks and then you only need to polish what he creates by giving him instructions on the PR he creates |
No description provided.