Following on from this, it seems that the PerlTransHandler looked like my best bet, but it doesn’t seem to be able to alter the hostname (please correct me if there is a way to do this, as I struggled with it so far)
I guess mod_rewrite allows the hostname to be altered, but I need to intercept the request and perform access checks, and I don’t know if I can do this before mod_rewrite kicks in during the request lifecycle. Quoting Dan Horne <[EMAIL PROTECTED]>: > Hi all > > I’m sure that this has been asked before, but I couldn’t seem to find the > right > terms when searching the archive. > > We have a website (not written in Perl or mod_perl), where we would now like > to > protect certain parts of the content. The business is loath to change the > architecture, as there are a number of hardware cache boxes that cache the > site, and they aren’t user-aware. > > My first reaction is to put a mod_perl handler on a set of servers in front > of > the system. Whenever a request for a page would come in, the handler would > check to see whether the page is private or public and would take the > appropriate action. Once a page has been requested for the first time, it’s > public or private status would be recorded in a simple perl cache. > > Now, my problem is as follows. I’m assuming that the current website address > will point to the new handler server(s). But after > authentication/authorisation > simply redirecting the user to the internal servers will now no longer work – > plus we don’t want the URL to change if possible. Is there a way that we can > accomplish this aim? > > Dan > > > -- > Report problems: http://perl.apache.org/bugs/ > Mail list info: http://perl.apache.org/maillist/modperl.html > List etiquette: http://perl.apache.org/maillist/email-etiquette.html > > > -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
