I have often used the same TransferLog entry in two different <Virtual Host 
...> entries without problem.  ErrorLog as well.  This will have the effect of 
combining log messages.

Rick

> Hi,
> 
> Different logfiles are required for SSL and the non-SSL connections because
> you have two different VirtualHost sections, and the logging commands are
> per-VirtualHost.
> 
> I created a patch to mod_ssl which allowed one VirtualHost section to handle
> both SSL and non-SSL connections. This allows you have only one logfile
> (which saves on file-descriptors) and keeps you from duplicating all of the
> configuration details.
> 
> I sent this to the list back on Fri 1/8/99 in a post entitled "New feature:
> SSLOnlyOnPort". Last I talked to Ralf he was working on implementing
> equivalent features in the main source tree. He was using the "SSLListen"
> directive name. I've not been keeping up with the list, so this may have
> already been added in.
> 
>  - David Harris
>    Principal Engineer, DRH Internet Services
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Martin Kuzela
> Sent: Monday, February 15, 1999 1:34 PM
> To:   [EMAIL PROTECTED]
> Subject:      one log file question
> 
> Hi all
> 
> When I want to analyze "access_log" file it generates wrong results because
> non-ssl accesses are in "access_log" and ssl accesses are in
> "access_log-ssl" and
> "ssl_log".
> 
> Can I configure mod-ssl to log both kind of access into "access_log" ?
> 
> thanks
> 
> Martin Kuzela
> 

______________________________________________________________________
Apache Interface to SSLeay (mod_ssl)   www.engelschall.com/sw/mod_ssl/
Official Support Mailing List               [EMAIL PROTECTED]
Automated List Manager                       [EMAIL PROTECTED]

Reply via email to