Yichun Zhang
Yichun Zhang
@splitice Patches welcome :)
@splitice Agreed :)
@huuuunt The error message clearly indicates that you have not defined any resolvers in your nginx.conf. See http://nginx.org/r/resolver for details.
@ryannining Yes, you need to test the MIME type before taking any action. `lua-resty-upload` implements its own request body reader while `ngx.req.read_body()` uses nginx's request body reader.
@ryannining You can just try calling `resty.upload`'s new() method first. Which performs the MIME test. If the test fails, `new()` returns `nil` with an error string. Under the hood, it...
@Roycohen The simplest way is just to write a simple PHP C extension library including the core C functions for encryption/decryption in this nginx C module.
We also tested thoroughly against 1.19.3.
On Fri, Nov 11, 2011 at 6:04 PM, cfsego [email protected] wrote: > in v1.1.0 You mean nginx 1.1.0? What're your versions of libdrizzle and ngx_drizzle? > conf is > upstream...
@fc28222 You can just re-generate the session value yourself. The expiration timestamp is directly encrypted into the session data itself.
I'm kinda worried about the lack of semaphore fallbacks. This may lead to undesired high CPU usage when lock contention is high (like lots of writes on huge trees).