Does the proxy-logging code use the eventlet.wsgi posthook for the logging?
>From a quick inspection of the code, it seems to add a generator to the
filter layers passing the object along. Could we avoid that by using the
posthook? Or was there some other reason for not using the posthook?
On Thu
Yep, im planning to debug the current middleware to see if i can submit a
fix or find my real problem and if it gets to dirty go to custom logging
code
Thanks pete
Any other experiences will be very appreciated :)
On Thu, Jan 10, 2013 at 2:59 PM, Pete Zaitcev wrote:
> On Thu, 10 Jan 2013 12:3
On Thu, 10 Jan 2013 12:37:57 -0300
Leandro Reox wrote:
> When we turn off the proxy-logging middleware, everything starts to
> response like a charm 8ms or so vs 800-1400ms !!!
At a guess, maybe the proxy-logging middle accidentially tries
to resolve an IP address somewhere?
> And i cant find t
Hi all,
We're having a problem when we migrated from 1.4.8, 1.7.4 , and we
activated the the proxy-logging middleware
On the proxy.log itself we're seeing excelent response times, but it seems
that is adding some overhead somewere cause we are seeing on the reques
originator that the times are re
4 matches
Mail list logo
