Instead of using http://192.168.1.10:1111/foo you can enter http://:1111/foo and Muximux will load page from the current host with the path and port specified appropiately. User is also able to specify login and password e.g. ftp://user:password@:1211/foo will be evaluated into ftp://user:password@192.168.1.10:1211/foo.
Real world use case
Let's consider the following scenario: Apache+PHP exposes Muximux on both interfaces: 192.168.1.10 and 10.0.1.10. The services which will be available through Muximux are also exposed on both interfaces. Using current version of Muximux, one would have to have two Muximux instances with separate configurations for each of interfaces. This patch allows to have Muximux available on all interfaces with shared configuration, and services defined with relative paths and ports.
Intro
Instead of using
http://192.168.1.10:1111/fooyou can enterhttp://:1111/fooand Muximux will load page from the current host with the path and port specified appropiately. User is also able to specify login and password e.g.ftp://user:password@:1211/foowill be evaluated intoftp://user:password@192.168.1.10:1211/foo.Real world use case
Let's consider the following scenario: Apache+PHP exposes Muximux on both interfaces: 192.168.1.10 and 10.0.1.10. The services which will be available through Muximux are also exposed on both interfaces. Using current version of Muximux, one would have to have two Muximux instances with separate configurations for each of interfaces. This patch allows to have Muximux available on all interfaces with shared configuration, and services defined with relative paths and ports.