For multiple intranet hosts,
my understanding the best way
to do it is to install a TIS proxy server on you linux
box --- with nothing to do with apache/modperl.
see the http://www.tis.com/ for details.
let me know if it works for you, pls.
Gordon Wu <[EMAIL PROTECTED]>
System Infrastructure
Global Derivatives Application Development
CitiBank, New York
Tel: (212)783-6838
> -----Original Message-----
> From: Jonas Nordstrom [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 05, 2000 10:35 AM
> To: [EMAIL PROTECTED]
> Subject: RE: external access to intranet
>
>
> Ok, but the problem is that we have more than one intranet
> host, and files
> at one host may call another and so on.
> If I've understood it correctly, ProxyPass requires you to
> have the same
> number of external servers and internal servers? Can
> Apache::RewritingProxy
> handle this?
>
> /Jonas
>
> > -----Original Message-----
> > From: darren chamberlain [SMTP:[EMAIL PROTECTED]]
> > Sent: den 5 april 2000 16:30
> > To: Jonas Nordstrom
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: external access to intranet
> >
> > Jonas Nordstrom ([EMAIL PROTECTED]) said something to this
> > effect:
> > > But doesn't that only pass on the request and then return
> the HTML-files
> > > unchanged? I also want to change the links inside the
> HTML-bodies on the
> > > fly, so that the users can continue to "surf the
> intranet". For example,
> > if
> > > the HTML contains "<A HREF="path/my_file.html">" I want
> to change that
> > to
> > > "<A HREF="https://gateway_server/intranet_host/path/myfile.html>"
> > >
> > > /Jonas
> >
> > Hi Jonas,
> >
> > ProxyPass does *not* modify the contents of the file (in
> fact, the docs
> > say
> > that it might not be all that useful for exactly this
> reason). The thing
> > is,
> > though, that the links, if relative, will be relative to
> the current page,
> > wherever that current page is. If your links are all in the form
> > <a href="../foo.html"> and <a href="./bar/baz.html"> then
> all links will
> > work just fine (this is a good idea anyway, although difficult to do
> > consistently).
> >
> > Assuming that you don't want to rewrite the pages on your
> intranet to fix
> > all your links (which is the point of this whole thing, I
> would assume),
> > then
> > the best way to do it, I would say, would be write a
> translation handler
> > that
> > would use LWP to fetch the document from the intranet
> server (possibly
> > with
> > some caching), pass it through a regex that fixes the links
> (i.e., preface
> > all
> > links with 'http://gateway_server/intranet_host/' unless
> they begin with
> > http),
> > and then send it to the browser. This is similar to the
> proxy module that
> > is
> > described in Chapter 7 of the Eagle book (p 374-381, or
> > http://www.modperl.com/book/chapters/ch7.html).
> >
> > Hope this helps.
> >
> > darren
> >
> > --
> > Friends help you move. Real friends help you move bodies.
>
