Updated Reverse Proxy Diagnostics Troubleshooting (markdown)

Reverse-Proxy-Diagnostics-Troubleshooting.md

@@ -67,6 +67,62 @@ httpd_can_network_connect --> on
 
 ## Send request via "reverse proxy"
 
+If reverse proxy configuration for "radicale" is configured in the default web server, URI must be extended to avoid any overlap conflicts
+
+Example config excerpt
+
+```
+# Apache
+  <Location /radicale>
+     ProxyPass        http://localhost:5232/ retry=0
+     ProxyPassReverse http://localhost:5232/
+     ...
+  </Location>
+```
+
+Example URLs to request
+
+```
+Radicale direct        : http://localhost:5232/.web/
+via reverse proxy      : http://localhost:80/radicale/.web/
+via reverse proxy (SSL): https://localhost:443/radicale/.web/
+```
+
+Only in case a dedicated virtual host (dedicated port or FQDN) is configured, the URI extension can be left-out in the reverse proxy configuration
+
+Example config excerpt for dedicated port, for FQDN configure name-based virtual hosting.
+
+```
+# Apache
+Listen 8080
+<VirtualHost _default_:8080>
+  ...
+  <Location />
+     ProxyPass        http://localhost:5232/ retry=0
+     ProxyPassReverse http://localhost:5232/
+     ...
+  </Location>
+</VirtualHost>
+
+Listen 8443 https
+<VirtualHost _default_:8443>
+  ...
+  <Location />
+     ProxyPass        http://localhost:5232/ retry=0
+     ProxyPassReverse http://localhost:5232/
+     ...
+  </Location>
+</VirtualHost>
+```
+
+Example URLs to request
+
+```
+Radicale direct        : http://localhost:5232/.web/
+via reverse proxy      : http://localhost:8080/.web/
+via reverse proxy (SSL): https://localhost:8443/.web/
+```
+
 ### Webserver "Apache"
 
 Example for unsuccessful request blocked by SELinux