Yichun Zhang

@rzenker Thanks for looking into this. Unfortunately this is not sufficient. We need to parse the chunked encoded data ourselves (we could reuse the chunked request body parser in the...

@rzenker Well, 1. I never wrote any resty-http libraries. You must be referring to some 3rd-party libraries. 2. I don't think it's really useful to expose the chunked encoding to...

@rzenker That lua-resty-http library is written by @pintsized and is a 3rd-party OpenResty library. It was used for upstream HTTP communications, instead of downstream (and we're talking about downstream here)....

@rzenker For your use case, you can just assemble the chunked body yourself. That overhead is minimal. I don't see a reason to give you the original chunked data just...

@aviramc Thank you for the update! Yeah, sometimes I found myself want this feature as well :) I'll look into this as soon as I can :)

@aviramc Will you mind adding some test cases for this feature? Otherwise it looks good to me :)

@StephanDollberg What's you use case of this? Maybe you should just manipulate the `Connection` request header via `ngx.req.set_header()` and `ngx.req.clear_header()`?

@NotYoCheese Maybe you use special characters in the memcached keys? This library encodes the keys by URI escaping sequences by default. You can turn that off. Read the docs please.

@NotYoCheese If it's not that problem, then please provide a minimal and standalone example that we can easily run and reproduce the problem on our side. Just try removing as...

Clearing means deleting the whole header entry, including names. It's easier to try it out yourself BTW.