Hi, I just installed ATS 2.1.4 on fresh ubuntu 10.01. In config I only changed timeouts, proxy port and allowed transparent proxy. Same problem - no host in log. Not possible to analyze logs. Hope you will have time to look at this in 2011 :)
Merry Christmas and Happy New Year! On Thu, 16 Dec 2010 16:19:15 -0700, Leif Hedstrom <[email protected]> wrote: > On 12/16/2010 12:08 AM, [email protected] wrote: >> Thanx, I found rolling option, it is really documented in admin guide. >> I am running ATS 2.1.4-unstable, transparent mode. I have no rules for Host: >> header (actually, I >> even do not know how to create them and why). traffic_logcat produces 2 >> kinds of records: w/o >> server and with server after DIRECT. > > Hmmm, maybe something then with transparent proxy, I haven't really > spent a lot of time testing it. Alan, any thoughts on these issues? > Anything in the logs that would cause our tools not to properly handle > the "host" ? > > -- leif > >> 1292482820.160 240 192.168.108.98 TCP_MISS/200 491 GET >> http:///data/mail.js?yaru=y - >> DIRECT/www.yandex.ru text/javascript - >> 1292482820.220 20 192.168.108.98 TCP_HIT/200 705 GET >> http:///jquery-1-4-2.crossframeajax.html - >> NONE/- text/html - >> >> >> On Tue, 14 Dec 2010 14:00:08 -0700, Leif Hedstrom<[email protected]> wrote: >>> On 12/14/2010 12:30 PM, [email protected] wrote: >>>> Sorry, forgot yet another question. ATS rotates log everyday, how do I >>>> change it to rotate >>>> weekly? Can't find the option in records.config... >>> CONFIG proxy.config.log.rolling_interval_sec INT 604800 >>> >>> >>> You can also roll on size of the log files etc., fairly certain it's >>> documented in the Admin guide? >>> >>> >>> As for your other problem, do you have some rule that matches on >>> requests without Host: headers? What version of ATS are you using? I'm >>> not seeing anything like that in my run of logcat. What is odd is that >>> traffic_logstats ought to show the same as traffic_logcat, logstats will >>> just parse the data in some different ways (but it'd require the same >>> "host" information in the URL to work). >>> >>> -- leif >>
