Re: [gentoo-user] Full path in apache2 access_log?
Ive played with many ecommerce packages (OSC, intershop, home-grown stuff in Perl, PHP and ASP). Recently built a site using Mambo (err... that should be called Joomla now ;-) and a plugin callead mambo-phpshop. The plugin has a complete backend already built so you just customize a few pages... Interchange sounds more like a framework that needs more work to build a complete store, right? I think you've hit upon the point that really makes Interchange cool. It is a great framework, but there are a few demo stores built on top of it that can be customized into your store in no time: http://demo.icdevgroup.org/i/demo1 http://demo.icdevgroup.org/i/demo2 I prefer to go the route of only using the basic framework and then creating my own stuff on top of that. Interchange is awesome either way, and you could easily set up your store on top of a demo store, and then customize it more and more as time goes on. - Grant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Full path in apache2 access_log?
Try adding %f and/or %{Host}i to the LogFormat directive. Or maybe one
of the others will give you the information you need:
http://httpd.apache.org/docs/2.0/mod/mod_log_config.html#formats
--
Michael Stewart [EMAIL PROTECTED]
Gentoo Developerhttp://dev.gentoo.org/~vericgar
GnuPG Key ID 0x08614788 available on http://pgp.mit.edu
--
signature.asc
Description: OpenPGP digital signature
Re: [gentoo-user] Full path in apache2 access_log?
On Thu, 3 Nov 2005, Grant wrote: Yeah, I wasn't very clear about that. The problem is I can't use VirtualHost definitions because I don't think apache knows which domain is actually being served. I don't use any apache virtual host stuff. Domain identification is handled by my shopping cart software. But presumably the shopping cart software merely looks at the URL you are coming from right? (What software is it? Does it run locally or is it on a remote server?). -- Aj. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Full path in apache2 access_log?
Yeah, I wasn't very clear about that. The problem is I can't use VirtualHost definitions because I don't think apache knows which domain is actually being served. I don't use any apache virtual host stuff. Domain identification is handled by my shopping cart software. But presumably the shopping cart software merely looks at the URL you are coming from right? (What software is it? Does it run locally or is it on a remote server?). The shopping cart software does only look at the URL, but I have it determining what to display partially based on the domain in that URL. apache2 doesn't do anything based on the domain. The shopping cart software is open-source Interchange, but the stuff I'm talking about here is custom-programmed in ITL (Interchange Tagging Language) for non-standard operation. http://icdevgroup.org Interchange is awesome and I highly recommend it, but I have to mention its steep learning curve. apache2, Interchange, etc. are all run on the same remote server. - Grant -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Full path in apache2 access_log?
On Wed, 2 Nov 2005, Grant wrote: Is there any way to get apache2 to include a full path in its access_log? That would be something like this: domain.com/page.html instead of this: /page.html If I can get a full path in the log, I can have webalizer report on traffic per domain. The conventional method of using the vhost log format for something like this won't work for me because it relies on defining different ServerName directives via VirtualHost definitions but I don't think apache knows which domain is actually being served. I don't use any apache virtual host stuff. Domain identification is handled by my shopping cart software. Maybe I dont understand what you mean: but since you are using VirtualHost definitions, then perhaps you could use separate logs for each site? e.g. VirtualHost site1.com ServerName www.site1.com ErrorLog /var/log/apache/site1_error.log AccessLog /var/log/apache/site2_access.log /VirtualHost VirtualHost site2.com ServerName www.site2.com ErrorLog /var/log/apache/site1_error.log AccessLog /var/log/apache/site2_access.log /VirtualHost I just avoid the whole logsplit issue by doing this on production servers. -- -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Full path in apache2 access_log?
Is there any way to get apache2 to include a full path in its access_log? That would be something like this: domain.com/page.html instead of this: /page.html If I can get a full path in the log, I can have webalizer report on traffic per domain. The conventional method of using the vhost log format for something like this won't work for me because it relies on defining different ServerName directives via VirtualHost definitions but I don't think apache knows which domain is actually being served. I don't use any apache virtual host stuff. Domain identification is handled by my shopping cart software. Maybe I dont understand what you mean: but since you are using VirtualHost definitions, then perhaps you could use separate logs for each site? e.g. VirtualHost site1.com ServerName www.site1.com ErrorLog /var/log/apache/site1_error.log AccessLog /var/log/apache/site2_access.log /VirtualHost VirtualHost site2.com ServerName www.site2.com ErrorLog /var/log/apache/site1_error.log AccessLog /var/log/apache/site2_access.log /VirtualHost I just avoid the whole logsplit issue by doing this on production servers. Yeah, I wasn't very clear about that. The problem is I can't use VirtualHost definitions because I don't think apache knows which domain is actually being served. I don't use any apache virtual host stuff. Domain identification is handled by my shopping cart software. - Grant -- gentoo-user@gentoo.org mailing list
[gentoo-user] Full path in apache2 access_log?
Is there any way to get apache2 to include a full path in its access_log? That would be something like this: domain.com/page.html instead of this: /page.html If I can get a full path in the log, I can have webalizer report on traffic per domain. The conventional method of using the vhost log format for something like this won't work for me because it relies on defining different ServerName directives via VirtualHost definitions but I don't think apache knows which domain is actually being served. I don't use any apache virtual host stuff. Domain identification is handled by my shopping cart software. - Grant -- gentoo-user@gentoo.org mailing list
