httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph S D Yao <>
Subject Re: [users@httpd] Problem with <Proxy> configs
Date Sat, 23 Aug 2008 23:27:49 GMT
On Sat, Aug 23, 2008 at 12:40:13AM -0500, William A. Rowe, Jr. wrote:
> Joseph S D Yao wrote:
> > 
> > I have just joined this mailing list, but a Google indicates that this
> > topic has not come up before.  If I am wrong, I apologize, and ask for a
> > pointer.
> Good way to attract attention of lurkers :)


> > I understand that the argument to the Proxy directive is supposed to be
> > a shell-style wildcard (rather than a simple prefix match), as the
> > argument to the ProxyMatch directive is supposed to be a Perl-style
> > regular expression.
> Ok.  So a shell style wildcard never hits on a path delimiter, right?

That depends on what "shell-style wildcard" means in a given
implementation.  I have seen ones where the path delimiter is not a
special character.  As the '/' is (a) not solely a path delimiter and
(b) not the unique path delimiter, in a URL, I had not expected that to
be a special character here.

In fact, noting that a "*" will match
"", I rather suspect that
it is not.

> >     <Proxy http://**>
> Perhaps you meant http://**
> But the trailing * is redundant.  drop it all together.

Yours does not accept the common usage, "", with no
trailing '/'.  Most Web servers will accept and correct this.

It is not clear to me that the "*" is redundant.  Without it, don't I
restrict myself to the home page?  All examples I have seen used with
<Proxy> that are not using "*" end in '*'.

** Joe Yao - Joseph S. D. Yao

The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message