3 ms·
Indeed I am wary of rewrite from apache days. So using a subdomain should solve routing issues - api.myproject.myorg.org instead of myproject.myorg.org/api ?
by sireat 3y ago
Indeed I am wary of rewrite from apache days.
So using a subdomain should solve routing issues - api.myproject.myorg.org instead of myproject.myorg.org/api ?
Two issues - my wildcard cert is *.myorg.org so not 100% it would cover subdomains of subdomains.
Second issue - you'd need to set up DNS for subdomain of subdomain, would you not?
Sadly DNS setup would require opening an uncertain to complete support ticket in myorg...
- e12e 3y agoAh, I assumed you already had subdomains set up. Path based routing should be fine, but you probably still don't need rewriting - just "mount" the appropriate proxies in appropriate location blocks (read over the examples in the documentation carefully).
- e12e 3y ago> my wildcard cert is *.myorg.org so not 100% it would cover subdomains of subdomains. it won't: https://www.rfc-editor.org/rfc/rfc2818#section-3.1 https://www.rfc-editor.org/rfc/rfc2818#section-3.1 > Matching is performed using the matching rules specified by [RFC2459]. If more than one identity of a given type is present in the certificate (e.g., more than one dNSName name, a match in any one of the set is considered acceptable.) Names may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., *.a.com matches foo.a.com but not bar.foo.a.com. f*.com matches foo.com but not bar.com.