Hello!
On Wed, Mar 18, 2015 at 12:21 PM, Lord Nynex wrote:
> This is sub-optimal if you need to talk to many different ssl targets, but
> is incredibly fast/efficient for a single upstream target. The reason is,
> you get all the benefit of upstream keep alive connections which avoids
> having to re-establish the SSL connection on every request.
>
Well, just to be clear: ngx_lua's SSL cosocket API also supports both
connection pooling and SSL session reuse so you don't have to redo SSL
handshake upon every request either ;) This is not really an advantage
of ngx_proxy over ngx_lua cosockets at all.
One problem with ngx.location.capture is that it's very inefficient
(and also dangerous) for responses that could be huge (like hundreds
of megabytes or even gigabytes) because it always mandates full
buffering of the response.
Regards,
-agentzh
