You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2015/06/01 11:21:53 UTC

[Bug 57978] New: unix:/ works with any number of / slashes except 2

https://bz.apache.org/bugzilla/show_bug.cgi?id=57978

            Bug ID: 57978
           Summary: unix:/ works with any number of / slashes  except 2
           Product: Apache httpd-2
           Version: 2.4.12
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mod_proxy_fcgi
          Assignee: bugs@httpd.apache.org
          Reporter: rainer-apache@7val.com

ProxyPassMatch or RewriteRules that reference Unix Domain Sockets do not work
if unix: is followed by exactly two slashes. Any other number (including zero,
resulting in a path relative to the ServerRoot) appears to work. 

If two slashes are used (as in "unix://"), the first path component is removed.
For example, the following two methods to specify an FCGI proxy with unix
domain sockets

RewriteRule ^\/\/?test.fit$
unix://home/canavan/foo/run/php-fpm.sock|fcgi://localhost//home/canavan/foo/htdocs/engine/test.fit
[P,L]

ProxyPassMatch ^/(.*)$
"unix://home/canavan/foo/run/php-fpm.sock|fcgi://localhost//home/canavan/foo/testhost/staticwww"

result in 503 errors and a message in the error log as follows:

[Mon Jun 01 11:12:45.124529 2015] [proxy:debug] [pid 13534:tid 139897419593472]
proxy_util.c(2226): [client 127.0.0.1:47978] AH02545: fcgi: has determined UDS
as /canavan/foo/run/php-fpm.sock

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 57978] unix:/ works with any number of / slashes except 2

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57978

Rainer Canavan <ra...@7val.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |---

--- Comment #2 from Rainer Canavan <ra...@7val.com> ---
I would argue that the (optional) authority part of the URI is obviously not
useful for the unix: scheme, and thus unix:/foo and unix://foo should be
equivalent.

Alternatively, apachectl configtest should reject any configuration that
references unix: URIs with an authority.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 57978] unix:/ works with any number of / slashes except 2

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57978

Szőgyényi Gábor <sz...@freemail.hu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |szg0000@freemail.hu

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


[Bug 57978] unix:/ works with any number of / slashes except 2

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57978

AR <an...@yandex.ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from AR <an...@yandex.ru> ---
This is not a bug.
General qualified URI scheme is:

<scheme>:[ "//" [ <hostname> ] ] <path>

Thus, 

protocol:something - local relative path (implementation-dependent, do NOT rely
on this functionality);
protocol:/something - local absolute path;
protocol://something - unknown path on remote host "something" (commonly
considered equivalent to "protocol://something/", i.e. root path on "something"
host);
protocol:///something - absolute path on unnamed(=local) host (also often seen
the more explicit form "protocol://./something"; since FQDN name ends in a dot,
a lone dot represents an empty name).

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org