No, it would produce http://www.example.comindex.html
The directive allows for optional trailing slashes for flexibility, i.e. Redirect /foo http://www.example.com/bar On Sat, Feb 24, 2018 at 5:29 PM, @lbutlr <krem...@kreme.com> wrote: > The syntax for redirect treats > > Redirect / http://www.example.com > > as a request to redirect, for example, index.html as " > http://www.example.com.index.html"; > > Since I can't think of any reason that this could possibly be desired, it > seems the parser should understand that when only a FQDN is specified with > a URL scheme, the final '/' is assumed. > > this would still allow for http://www.example.com/new formats, etc, and > would only apply to the specific format xxxx://FQDN > > (Although I think even this syntax should assume a final / and that if the > "append . and location" behavior is wanted the format should be > > http://www.example.com/new. > > But that would possibly break existing configs for no real gain. > > > -- > Lisa Bonet ate no Basil > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
