This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
To: "Modperl Mailing List (E-mail)" <modperl@apache.org>
From: "Christian Gilmore" <cgilmore@tivoli.com>
Subject: [ANNOUNCE] Apache::ProxyRewrite 0.10
Date: Tue, 2 Jan 2001 18:01:21 -0600
The uploaded file
Apache-ProxyRewrite-0.10.tar.gz
has entered CPAN as
file: $CPAN/authors/id/C/CG/CGILMORE/Apache-ProxyRewrite-0.10.tar.gz
size: 10759 bytes
md5: eb5a80cb7ded3e41705382b371ae5015
Apache::ProxyRewrite acts as a reverse-proxy that will rewrite URLs embedded in HTML documents per apache configuration directives.
This module was written to allow multiple backend services with discrete URLs to be presented as one service and to allow the proxy to do authentication on the client's behalf.
See ProxyRewrite.pm pod for detailed documentation.
===
To: "Modperl Mailing List (E-mail)" <modperl@apache.org>
From: "Christian Gilmore" <cgilmore@tivoli.com>
Subject: [ANNOUNCE] Apache::ProxyRewrite 0.11
Date: Sun, 14 Jan 2001 13:55:11 -0600
The uploaded file
Apache-ProxyRewrite-0.11.tar.gz
has entered CPAN as
file: $CPAN/authors/id/C/CG/CGILMORE/Apache-ProxyRewrite-0.11.tar.gz
size: 10843 bytes
md5: 851e2561d7bcd9ef4fd20dd8cb735ad5
Apache::ProxyRewrite acts as a reverse-proxy that will rewrite URLs embedded in HTML documents per apache configuration directives.
This module was written to allow multiple backend services with discrete URLs to be presented as one service and to allow the proxy to do authentication on the client's behalf.
See ProxyRewrite.pm pod for detailed documentation.
2001-01-14 Christian Gilmore <cgilmore@tivoli.com>
o Added 'base' as an element of the LINK_ELEMENT hash
o Made release 0.11
2001-01-02 Christian Gilmore <cgilmore@tivoli.com>
o Made first public release 0.10
$Id: ChangeLog,v 1.2 2001/01/14 19:47:28 cgilmore Exp $
===
To: "Christian Gilmore" <cgilmore@tivoli.com>
From: Stephane Bortzmeyer <bortzmeyer@pasteur.fr>
Subject: Re: [ANNOUNCE] Apache::ProxyRewrite 0.11
Date: Mon, 15 Jan 2001 11:10:26 +0100
On Sunday 14 January 2001, at 13 h 55, the keyboard of "Christian Gilmore"
<cgilmore@tivoli.com> wrote:
> Apache::ProxyRewrite acts as a reverse-proxy that will rewrite URLs
> embedded in HTML documents per apache configuration directives.
>
> This module was written to allow multiple backend services with discrete
> URLs to be presented as one service
What about Javascript code? Or per-directory realms?
===
To: <bortzmeyer@pasteur.fr>
From: "Christian Gilmore" <cgilmore@tivoli.com>
Subject: RE: [ANNOUNCE] Apache::ProxyRewrite 0.11
Date: Mon, 15 Jan 2001 10:28:32 -0600
Stephane,
When you say per-directory realms, do you mean you want to be able to
define a ProxyAuthInfo variable multiple times? You can do that once per
front-end location. Currently, the ProxyAuthInfo variable is not tied to a
particular realm. Rather, it is tied to a particular URI.
As for javascript, if it is properly encased within HTML comments, it
won't be touched by the rewriting engine. If it dynamically generates URLs
on the fly, the likely case is that these URLs will be invalid or will
point directly to the backend, skipping the proxy. Two things about this:
1) If your front-end URI space maps directly onto your backend and the
javascript produces relative URIs, there shouldn't be a problem unless the
code is generating absolute URLs.
2) In order to handle all cases of dynamically rewriting javascript (or
any code, for that matter), one must first solve the halting problem. That
is an impossible task.
Regards,
Christian
===