I created a full reference guide for Omnissa Unified Access Gateway Web Reverse Proxy patterns, co-authored with
Chad Ingram, and published it on the Omnissa Community.
What it covers:
* Regex dialect — UAG patterns compile through Java regex, not PCRE or JavaScript, and the differences bite.
* Matching behavior — patterns evaluate the URI path only, anchored at both ends; this one rule causes most "it half works" tickets.
* Multi-proxy selection — how Proxy Pattern, Proxy Host Pattern, and instance order decide routing.
* Worked examples — several real configurations spanning Access, Horizon, WordPress on LAMP, sub-path hosting, Exchange, and the X-Forwarded header family.
* Troubleshooting — a checklist mapping common 404 symptoms to their root causes.
Several of these were built and broken in my lab before writing anything down. If you run UAG in front of anything beyond the documented Access example, it is worth a read:
https://lnkd.in/gegVVK-d
We welcome your feedback, corrections, and additional backend scenarios in the Omnissa Community thread, where Chad and I can fold them into the guide.
#Omnissa #UAG #WorkspaceONE #Horizon #EUC #ReverseProxy
UAG Web Reverse Proxy Patterns Explained: Regex Dialect, Path Matching, and Real-World Examples
UAG Web Reverse Proxy Patterns Explained: Regex Dialect, Path Matching, and Real-World Examples