httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Hartill <hart...@hyperreal.com>
Subject Another 'step' for Apache module translation? (fwd)
Date Tue, 10 Oct 1995 03:20:25 GMT

Take a deep breath....

ack sent.

Forwarded message:
> From cam@indy.mvbms.com  Mon Oct  9 09:37:59 1995
> Message-Id: <199510091625.QAA20423@indy.mvbms.com>
> Date: Mon, 09 Oct 95 12:25:23 -0400
> Sender: cam@indy.mvbms.com
> From: Cameron Elliott <cam@indy.mvbms.com>
> Organization: Elliott Productions
> X-Mailer: Mozilla 1.12 (X11; I; IRIX 5.3 IP22)
> MIME-Version: 1.0
> To: apache-bugs@apache.org
> Subject: Another 'step' for Apache module translation?
> X-URL: http://www.apache.org/bug_report.html
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain; charset=us-ascii
> 
> I would like to propose a post 'handler' step/phase for the
> Apache module interface.
> I need this to fully implement my URL cookie module without modifying
> source files such as http_*.c
> 
> I'm sure most reading this know what URL-cookies are, but if you are 
> unsure, please visit the site www.pathfinder.com, and notice the '@@....'
> junk in the URL, its a cookie that allows a clients visit through
> the site to be tracked, and allows the server to maintain state information
> about the clients session.
> 
> I realize that url-cookies not a pretty solution, and can affect how URL's
> were intented
> to be used, but I am aware of these ramifications, and so are others who use
> them.
> I believe that the gains from URL-cookies are much greater than the losses.
> (I proposed to submit url-cookie mods for 0.6.5, and Brian B. declined to take
> them, so I assume the group doesn't think they are too hot :)
> 
> Anyway, to complete the module without affecting source files like http_*.c,
> I need a post handler phase.
> Why?, well, the way my url-cookie module works is that it is a _handler for
> type '*/*', and the directory type.
> 
> Currently, it checks all uris for a cookie, if present, it removes it, and
> sets a flag (header) in the request* make note that the cookie was stripped, and
> performs an internal redirect.
> On the next pass through it sees the cookie stripped flag, and DECLINES to
> handle the request, thereby letting it fall through to the rest of the handlers.
> This works great, and the cookie module handles most typical site visits,
> except when a module performs a REDIRECT with an absolute URL, this causes the
> cookie to get lost and the mechanism to generate another cookie.
> For example, in mod_dir.c, and in mod_imap.c, there is does a REDIRECT with
> an absolute URL, this really causes the whole thing to crap out.
> So, if I had a post handler phase, I could look for the 'Location' header, 
> and re-insert the cookie if necessary.
> I know that some don't want the URL-cookie stuff around, but I really think 
> its useful, and I think another phase could be of use in situations like
> this that I am not aware of.
> 
> Please let me know what you think.
> Cameron Elliott
> cam@indy.mvbms.com
> (212)886-4443
> 
> 
> 


Mime
View raw message