cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <>
Subject Re: Cocoon2 Design
Date Mon, 05 Jun 2000 18:35:39 GMT
Neeme Praks wrote:
> > -----Original Message-----
> > From: Stefano Mazzocchi []
> > Sent: Friday, June 02, 2000 4:31 PM
> >
> > > Actually, how well is supported the "referral" feature:
> > together with
> > > the POST data the browser also sends the URL of the original page
> > > (poster)?
> >
> > You mean to do sessions? Sorry, I need a better example here to
> > understand what you mean.
> I mean the that when browser requests a page, it also sends the URL of
> the "referring" page that linked to the page being requested.
> Example with GET:
> ---- <page1.html> ----
> <a href='page2.html'>Click here!</a>
> ---- </page1.html> ----
> So, when the user clicks on the link, the browser send the request for
> "page2.html" and includes the URL ("page1.html") of the referring page.
> If I remember correctly, it is included in HTTP headers?

I think so, yes, but I'm not sure. Is this a standard requirement?

I know Apache is able to log those and some fancy log analyzers are able
to do "path" statistics to tell you where your users normally go (so you
can make banners targetted to them by analyzing their navigating

Anyway, if it's included in the HTTP headers, every action gets the same

> Useful, when you would like to return the user to the page he came from,
> after completing some action that doesn't produce any output.

Right, I understand now.

Headers should be orthogonal to the HTTP action requested.

Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<>                             Friedrich Nietzsche
 Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------

View raw message