Purl Gurl wrote:
> Tony wrote:
> > HansH wrote:
(snipped)
> > :: RewriteCond %{REQUEST_URL} !/"http://www.site.com/go-here.htm"
> > : Assuming that first slash is just a type _here_ ...
> > That wasn't a typo. I read an example
> > somewhere on google that the / was needed.
> /go-here.htm
<font color=purple> > <a style='text-decoration: underline;' href="http://www.site.com/go-here.htm</font" target="_blank">http://www.site.com/go-here.htm</font</a>>
> Those two immediately above, are the same request path.
> Typically, use of / should _not_ be followed by
> a http reference; that is already included by
> automagic default.
I need to qualify this. Be careful to not allow me
to confuse you on "document root" and "relative path"
syntax. Research and read about use of alias / syntax
and use of /child/directory/file.html as a relative
path syntax.
This is why I often suggest to readers to always use
a full path, never use a relative path. Doing so adds
great clarity and avoids confusion which is displayed
in my previous article by not qualifying completely.
There is another problem. If your machine, upon which
you are browsing the net, if your machine has Apache
running as a "localhost" system, relative paths in
html documents on the net, actually reference your
running localhost Apache resulting in 404 not found
errors popping up. This is severe problem when style
sheets (css) are used.
Use full paths, always, both internally to Apache
and in your webpages.
Purl Gurl<!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: RewriteCond on IP and endless loops