Normally I do this in Apache or nginx with a rewrite like this:
RewriteRule ^/(.*) http://localhost:8080/VirtualHostBase/https/yoursite.com:443/Plone/VirtualHostRoot/$1 [P,L]
Today I'm working with the TTW virtual_hosting (no access to configure the proxy).
Is there a way to set a mapping in {myinstance}/virtual_hosting/ so that https will work?
I figured it out, putting this in the virtual_hosting mappings worked for me.
example.com/VirtualHostBase/https/example.com/Plone
explanation:
example.com represents the URL of my site
/VirtualHostBase/https/example.com forces zope to serve example.com over https://
/Plone represents the path to my plone site
Would that "hinder" the Volto in any way? Would performance be worse?
I'm wanting to let Volto access Plone, but I'd like to access Plone directly, through a gateway, without going through an nginx. For gateway access to work with https, I would have to have the above solution. Is there another solution for this?
Not sure that it will make a difference. Best to try it.
My question is whether having an entry in virtual_hosting along with a VirtualHostBase in the URL will slow things down.
No. it goes through the same code either way. We run our production using all TTW virtual host monster config so we can change things quickly.
Wesley Barroso Lopes via Plone Community wrote at 2022-8-31 17:19 +0000:
My question is whether having an entry in virtual_hosting along with a VirtualHostBase in the URL will slow things down.
Likely a bit but probably not significantly.
If you really need to know, make measurements.