From: "Dmitry Akindinov" Received: by mx.demos.su (CommuniGate Pro PIPE 5.0.14) with PIPE id 548297156; Sat, 29 Dec 2012 09:46:00 +0400 X-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD, SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2-st1.demos X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 3.3.2-st1.demos (2011-06-06) X-Spam-Report: -1.3 points, 5.0 required; * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * -0.0 SPF_PASS SPF: sender matches SPF record * -0.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain * -0.5 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list Received: from moscow.stalker.com ([89.175.185.228] verified) by mx.demos.su (CommuniGate Pro SMTP 5.0.14) with ESMTP id 548297163 for CGatePro@mx.ru; Sat, 29 Dec 2012 09:45:55 +0400 Received: from [37.204.163.96] (account dimak@mail.moscow.stalker.com HELO [192.168.0.112]) by mail.moscow.stalker.com (CommuniGate Pro SMTP 6.0.1o) with ESMTPSA id 35730259 for CGatePro@mx.ru; Sat, 29 Dec 2012 09:45:50 +0400 Message-ID: <50DE8384.8040909@stalker.com> Date: Sat, 29 Dec 2012 09:45:40 +0400 Organization: Stalker Labs User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: CommuniGate Pro Russian Discussions Subject: Re: [CGP] HTTPA References: <50D95F62.6090208@rsu.edu.ru> In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit Здравствуйте, On 2012-12-29 09:10, Kwam wrote: > В 6.0 заход в HTTPA порождает в логах кучу сообщений типа > > 09:00:06.195 2 TLS-000361 session released 09:00:44.444 2 TLS-000366 > created(TLSv1.0,RC4_SHA) for HTTPA-000040 09:00:44.444 2 TLS-000367 > created(TLSv1.0,RC4_SHA) for HTTPA-000039 09:00:44.492 2 TLS-000367 > closed by HTTPA-000039, refCount=1 09:00:44.492 2 TLS-000366 closed by > HTTPA-000040, refCount=1 09:00:46.561 2 TLS-000368 [] > Как сделать эти логи менее детальными, но более информативными? Установите уровень лога WebAdmin -> Settings -> Services -> HTTPA в Failures. Более детальный лог нужен, если вы подозреваете какую-то проблему в работе модуля. -- Best regards, Dmitry Akindinov