[Lula] httpd.conf redirect / authorization mix

[nix.slayer at charter.net]

Peter Benjamin wrote:

>Redirects can be done 3 ways:
>
>Via a mod_rewrite command (the hard way - but given you have
>an existing site with existing bookmarks distributed around
>the world, which you may also wish to redirect, then rewrite
>rule is the way to go.  But if not, then do not use this method).
>
>Via the directive "Location" - the easy apache config method.
>http://httpd.apache.org/docs/2.2/mod/core.html#location
>
>Or via the META tag refresh method, done in inside the home page.
>This is a good temporary method, or even permanent, if you do
>not wish to impact your apache config file with such.
>
>A fourth method is with the CGI NG script method of issuing
>a HTTP "Location: URL" command.  This is considered better
>than the META tag, or was years ago, when not all browsers
>support META tags.
>
>All these methods work the same way, that is the HTTP
>Location command is issued back to the browser, and
>the browser goes to the new URL, without letting the
>web surfer prevent this behavior.
>
>Web questions are better posted to the LAMPsig.org mailing list.
>LAMPsig was founded by LULA members who wanted to focus on web
>technology for professionals.
>
>_______________________________________________
>Lula mailing list
>Lula at lula.org
>http://www.lula.org/mailman/listinfo/lula
>
>  
>
Just wanted to add a small caveat: mod_rewrite is great but I've seen it 
not work properly in some environment where teh app was coming off a 
J2ee engine.  We have to go tinker with the application itself to get it 
to show the external FQDN, instead of the internal FQDN (that should've 
been masked) that was breaking links at the public (external) website.
_______________________________________________
Lula mailing list
Lula at lula.org
http://www.lula.org/mailman/listinfo/lula