Facebook
Twitter
TimReeves
Regular Pleskian
I just started a new thread about some shortcomings in the nginx config when setting "Proxy Mode: Off". I never imagined that Plesk would still generate an httpd config for that domain. Now I checked - and well I'll be, it does!
That given, I can't see any advantage in the new option "Proxy mode". It does not retract the httpd config for the domain, and instead of a "location / {...}" proxy-pass block - which I could get around by specifying own locations to catch all expected forms of URI - now I get a "location ~ \.php(/.*)?$ {...}" block, which pre-empts anything I could put in my custom config file to catch .php files myself.
I find this really really disappointing.
It seems I still have no option to get what I need, short of creating TWO custom templates.
That given, I can't see any advantage in the new option "Proxy mode". It does not retract the httpd config for the domain, and instead of a "location / {...}" proxy-pass block - which I could get around by specifying own locations to catch all expected forms of URI - now I get a "location ~ \.php(/.*)?$ {...}" block, which pre-empts anything I could put in my custom config file to catch .php files myself.
I find this really really disappointing.
It seems I still have no option to get what I need, short of creating TWO custom templates.
Last edited: