On Wed, 30 Oct 2002, Vadim Gritsenko wrote: > Where do you see it? > > > > .. Am I looking > >in the right place for referrer info, or am I way off? > > > > You need referer header which browser sents. Usually this info logged by > web server or server engine. You can either create your own log (action > logging value of the header) or use existing log of the web server or > servlet engine. > > Cocoon by itself do not write access log similar to log of the web > server, because cocoon does not tries to replace web server.
Vadim, I eventually tracked down that the referring URL *is* given in core.log, but only when the log level is set to debug in logkit.xconf. The thing that threw me off in this example was that for some reason the referrer was simply not being sent. I tested this by tailing the log and reloading a few times and noticed that the referrer was being sent. I poked around with my ideas of somehow pulling out the referring URL, and started looking at writing a ReferringURLAction. Off list, I emailed Christian Haul regarding some ideas, and he pointed out to me that there's the request InputModule which can let me access the referring url (or any header) by name. I guess it's time to add docs to the Wiki... On a side note, it would be nice to have some sort of simple access logs that followed the "tradition" Apache HTTPD-style logs. So much time, so little documentation, I guess :) Thanks for your help, Tony Tony Collen -- [EMAIL PROTECTED] College of Liberal Arts University of Minnesota, Minneapolis, West Bank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
