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
-----------------
Christian Gilmore
Infrastructure & Tools Team Lead
Web & Multimedia Development
Tivoli Systems, Inc.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, January 15, 2001 4:10 AM
> To: Christian Gilmore
> Cc: Modperl Mailing List (E-mail)
> Subject: Re: [ANNOUNCE] Apache::ProxyRewrite 0.11
>
>
> On Sunday 14 January 2001, at 13 h 55, the keyboard of
> "Christian Gilmore"
> <[EMAIL PROTECTED]> 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?
>
>
>
