Skye Poier Nott [EMAIL PROTECTED] writes:
I'm getting a lot of lines line this from varnishncsa:
10.151.1.1 - - [25/Nov/2008:19:11:14 +] GET http://
vectordevhttp://vectordev/devsite/diagrams/tn-rev1.png HTTP/1.1 200
60834 - curl/7.16.3 (amd64-portbld-freebsd6.3) libcurl/7.16.3
Maybe create a simple script to separate logs
Every URL is logged using http://domain/uri structure.
Really simple script to program.
Kitai
2008/11/26 Marcus Smith [EMAIL PROTECTED]:
Dear list,
I currently have a machine running Varnish (2.0.2) set up in front of
several different
David (Kitai) Cruz wrote:
Maybe create a simple script to separate logs
Every URL is logged using http://domain/uri structure.
Really simple script to program.
So you mean set varnishncsa to output everything to one log file (or
pipe), and then use something like sed or perl to split the
Marcus Smith [EMAIL PROTECTED] writes:
So you mean set varnishncsa to output everything to one log file (or
pipe), and then use something like sed or perl to split the log by
domain? If that's really the best way, then that's fine by me. I was
just hoping there might be a way of writing to
Dear list,
I currently have a machine running Varnish (2.0.2) set up in front of
several different websites. I would like to be able to collect access
logs for each of the different sites separately.
Obviously the Apache logs for these sites will be incomplete, as
varnishd will serve cache hits
Hi,
I have a site where users can log in. This sets a cookie with their
encrypted login details, so they can be authenticated. There are a
small number of pages which are user-specific (change your details
forms, etc), and these are set not to cache.
When a user is logged in, a message is
Hi,
I have a site where users can log in. This sets a cookie with their
encrypted login details, so they can be authenticated. There are a
small number of pages which are user-specific (change your details
forms, etc), and these are set not to cache.
When a user is logged in, a message is
Dag-Erling Smørgrav wrote:
Actually varnishncsa uses the same log filtering / selection code as
varnishlog, which *can* select requests based on URL. Extending
varnishncsa to do the same should not be too hard.
Other issues with varnishncsa / varnishlog: varnishlog doesn't allow -o
and -w
So, if i've got 900 domains, do i have to start 900 varnishlog processes?
Interesting:;-)
Kitai
2008/11/26 Marcus Smith [EMAIL PROTECTED]:
Dag-Erling Smørgrav wrote:
Actually varnishncsa uses the same log filtering / selection code as
varnishlog, which *can* select requests based on
Hello,
What about doing a massive ncsa log, then parse it for each domain with your
stats software ?
Or maybe splitting it in different logs in post production ?
--
Sébastien FOUTREL
Responsable Production
BCS Technologies
45 Rue Delizy
93692 PANTIN Cedex.
Bur : 01.41.83.17.20
Fax :
Sébastien FOUTREL wrote:
Hello,
What about doing a massive ncsa log, then parse it for each domain with your
stats software ?
Or maybe splitting it in different logs in post production ?
This was what Kitai suggested, and I agree that this would probably be
the best way to do it in the
Marcus Smith [EMAIL PROTECTED] writes:
Well in that case, is there any reason why I shouldn't simply do
something like:
varnishlog -c -o RxHeader Host: (www\.)?example1\.com
/path/to/logs/example1.log
varnishlog -c -o RxHeader Host: (www\.)?example2\.com
/path/to/logs/example2.log
Miles wrote:
Hi,
I have a site where users can log in. This sets a cookie with their
encrypted login details, so they can be authenticated. There are a
small number of pages which are user-specific (change your details
forms, etc), and these are set not to cache.
When a user is
Another approach is to simply use a small bit of Javascript. It's
easy to test for the existence of the cookie in Javascript and
set that text conditionally.
Then you have only one copy of the page to be cached.
The problem with the approach you've outlined here is
that other downstream caches
We do both depending on scenario: we use ajax to update parts of a page
after-delivery (poor mans ESI ;) as suggested by Tim, and we also have a
custom vcl_hash that caches different copies of pages depending on various
cookies and other conditions (much as Miles suggests). Both fit depending
on
Have a look at ESI:
http://varnish.projects.linpro.no/wiki/ESIfeatures
Regards,
Bjoern
Miles wrote:
Hi,
I have a site where users can log in. This sets a cookie with their
encrypted login details, so they can be authenticated. There are a
small number of pages which are user-specific
16 matches
Mail list logo
