I am looking at Reverse proxy for my site.
***The /owa make no sense for me. ***
Please refer to official Apache documentation for more information: https://httpd.apache.org/docs/2.4/mod/mod_proxy.html
*** That is what I did and found: ***
ProxyPass “/foo” “http://foo.example.com/bar”
ProxyPassReverse “/foo” “http://foo.example.com/bar”
Also there is another Google translation error?
“… A virtual host name rule can be forward HTTP requests to another web server…”
*** I think “be” sould not “be” there. ***
Why using “Virtual hosts” for one of the tabs of the page Reverse proxy?
Apache uses that name (with no space) but with NethServer (with space), il also refers to Virtual hosts" under Management. I found it very confusing at first.
Why using 2 pages with the same title to describe the same concept?
Why using a “.” instead of a “-” in a domain name?
On page: http://docs.nethserver.org/en/v7/proxy_pass.html#proxy-pass-section
- Requests matching an URL path, like
- Requests matching a virtual host name, like
*** For the path example, “http://mydomain.com/mysite” describes well the situation. “/mysite” looks like a path inside the web site
*** But for the virtual host example: “http://my.secondary-domain.com” is confusing. Is it the “my.” describing the virtual host, even if it looks like a subdomain for me? It should be “http://my-secondary-domain.com” which will make more sense in describing another web site.
I tried different way to test reverse proxy: Paths and Virtual hosts, green IP and red IP of target to no avail.
So I decided to use my SME server to see if it is a reverse proxy error or a target error. With SME, it works first shot. So it is the reverse proxy server.
It is while investigating that problem that I want to try the above example http://docs.nethserver.org/en/v7/proxy_pass.html.
Good and exact wording means everything if I want my grandmother to understand me correctly…