You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "@lbutlr" <kr...@kreme.com> on 2018/02/24 22:29:56 UTC
[users@httpd] Suggestion on Redirect parsing
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-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Re: Suggestion on Redirect parsing
Posted by Eric Covener <co...@gmail.com>.
On Sun, Feb 25, 2018 at 2:22 AM, @lbutlr <kr...@kreme.com> wrote:
> On 2018-02-24 (19:31 MST), Eric Covener <co...@gmail.com> wrote:
>>
>> I tried three different maintenance levels and they all produced
>> "Location: http://www.example.com" with that config and request.
>
> Yes, you're right. I was looking at logs where the initial path query started with a period. oops.
>
> Still, my point was that a scheme and a FQDN and nothing else could be interpreted as what is obviously intended without breaking anything and would save some people some grief.
I think it's reasonable.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
[users@httpd] Re: Suggestion on Redirect parsing
Posted by "@lbutlr" <kr...@kreme.com>.
On 2018-02-24 (19:31 MST), Eric Covener <co...@gmail.com> wrote:
>
> I tried three different maintenance levels and they all produced
> "Location: http://www.example.com" with that config and request.
Yes, you're right. I was looking at logs where the initial path query started with a period. oops.
Still, my point was that a scheme and a FQDN and nothing else could be interpreted as what is obviously intended without breaking anything and would save some people some grief.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Suggestion on Redirect parsing
Posted by Eric Covener <co...@gmail.com>.
On Sat, Feb 24, 2018 at 5:29 PM, @lbutlr <kr...@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"
I tried three different maintenance levels and they all produced
"Location: http://www.example.com" with that config and request.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
[users@httpd] Re: Suggestion on Redirect parsing
Posted by "@lbutlr" <kr...@kreme.com>.
On 2018-02-24 (17:16 MST), Frank Gingras <th...@apache.org> wrote:
>
> No, it would produce http://www.example.comindex.html
Not what I've seen. www.example.com is actually "www.example.com." as all domains are terminated by a '.', it just doesn't often have to be present.
> The directive allows for optional trailing slashes for flexibility, i.e. Redirect /foo http://www.example.com/bar
Which is not related to what I suggested.
--
I WILL STOP TALKING ABOUT THE TWELVE INCH PIANIST Bart chalkboard Ep.
3F07
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Suggestion on Redirect parsing
Posted by Frank Gingras <th...@apache.org>.
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 <kr...@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-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>