Re: [Rabbit-proxy-development] Re: Logging

[Robert O. <ro...@kh...>]

Rick Leir wrote:
> It is good that you used Measurement Factory's Co-Advisor Test Suite. Do 
> they let you re-run it from time to time?

Yes they do. They have been really nice about this.
I have not tested rabbit 2.x in some time, but then I have not made
any big changes in it either..

If you have checked any of the rabbit3 page the last month you would 
have noticed that I have run the tests for it, getting better over time.
At the moment rabbit 3 only have 1 thing (3 test cases) where it 
violates the specification and I am think that I want it that way. I am 
not sure yet and maybe with strict http mode rabbit 3 will be correct.
The case is that if rabbit get a request with a chunked or multi part 
resource rabbit has to provide a content length header when it passes it 
on unless rabbit can know that upstream is http/1.1 compliant. Knowing 
that a random web server is http/1.1 compliant is really not possible so 
what do I do? I can buffer the resource either in memory or on disk, but 
that will introduce latency and use prepare for some nice proxy DoS...

Last full test on Co-Advisor was on 6 february, 2006.

Anyway rabbit 3 has a bug in the nio handling, it will in some cases use 
100% cpu (I will fix that some day). So rabbit 3 is not ready for real 
use, yet. But please test it and tell me how it works.

About java.util.logging: I thought about it, but I am not sure that it 
is what I want. Note that in rabbit 3 it is very easy to implement your 
own log handler, perhaps I will add one logger based on your example and 
make it configurable.

/robo