From 15b02c5cac4b79ad921c5a5989316f19d6f57fbd Mon Sep 17 00:00:00 2001
From: nomandera <1133344+nomandera@users.noreply.github.com>
Date: Sun, 26 Jun 2022 16:35:16 +0000
Subject: [PATCH] Clarify subdomain vs subfolder proxying benefits

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 2ba74b2..110b24c 100644
--- a/README.md
+++ b/README.md
@@ -11,6 +11,12 @@ They are grouped in two:
 1. `subfolder` these will allow accessing services at https://yourdomain.com/servicename
 2. `subdomain` these will allow accessing services at https://servicename.yourdomain.com
 
+It is recommended that users deploy subdomain reverse proxying and not subfolder.
+
+Whilst subfolder reverse proxying appears easier to implement the inherent nature of this technique requires that each application developer make accommodations to support it. This is not always the case and it is common to see applications with no or partial support resulting in an unreliable experience.
+
+Conversely subdomain reverse proxying does not require special accommodation by application developers and will invariably work (or can be made to work) seamlessly without upstream changes.
+
 ## To enable the reverse proxy configs:
 
 ### Configure your default site config