2

The problem is not the order of execution - the directives are being executed in the order shown - but an issue with variable scope and cookie setting. The environment variables you set here are not going to be available to the target server, since this is a different scope. The cookie you are "setting" will not be available to your script in the ...


2

In my understanding and experience reverse_proxy takes precedence because directives have a default implicit order: https://caddyserver.com/docs/caddyfile/directives#directive-order . To force a different order you have at least 3 options: use a route: route /api/* { file_server reverse_proxy localhost:9000 } change the default order ...


1

The error is caused by your ProxyPass and ProxyPassReverse directives not having the scheme part of the URL. The correct syntax would be e.g. ProxyPass "/" "http://localhost/serv1" ProxyPassReverse "/" "http://localhost/serv1" However, Andrew is correct in that reverse proxy isn't required nor best technology for ...


1

How about just: <VirtualHost *:80> ServerName service1.site1domain.com DocumentRoot /var/www/html/serv1 </VirtualHost> <VirtualHost *:80> ServerName service2.site1domain.com DocumentRoot /var/www/html/serv2 </VirtualHost> No mod_proxy needed.


1

If I understood you correctly "endpoint" means the browser client? ("endpoint" usually means a web service endpoint, not the service consumer...) "Classic" HTTPS would not even allow the scenario you wish to happen. The hostname gets translated via DNS into ip:port(443) of the webserver and then TLS happens, which in early days ...


1

I have no access to web server config so I have to find this workaround. File lib/setuplib.php, line 900 in my case, Moodle comment of this: $CFG->sslproxy specifies if external SSL appliance is used (That is, the Moodle server uses http, with an external box translating everything to https). Change if (empty($CFG->sslproxy)) for if (!empty($CFG-&...


1

If your primary React app located under /var/www/html/storefront directory and you can put your dashboard app under /var/www/html/storefront/dashboard directory, the most simple way to do it is to use the following configuration: server { server_name shop.saleortest.com; root /var/www/html/storefront; # SSL configuration by certbot here ...


1

Solution: The problem was as "stupid" as it was hidden (so lesson learnt: never "just" include boiler plate.) The standard proxy.conf included (it is part of one of the nginx containers I tried) contains the following (which is a lot and probably contains unneeded stuff?): ## Version 2020/10/04 - Changelog: https://github.com/linuxserver/...


1

It's most of the time a good idea to reverse proxy applications and it's default behaviour in the most setup. It gives you flexibility, maintainability and security as well.


1

According to Krestel official documentation is a good practice to use a reverse proxy. The implementation doc is good and it goes into more details about it: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel?view=aspnetcore-5.0 If only one frontend server is powerful enough to maintain your workload I don't see any problem with that.


1

You can't use variables inside the regex patterns, all the regex patterns are compiled at the nginx startup, although you are free to use variables inside the strings that to be matched upon some regex pattern. This means the $systemname variable won't be evaluated when you use the rewrite (?i)/$systemname(.*) /target$1 break; Your location ~* /(?<...


1

$HTTP["host"] =~ "(www.)?somewebsite.com" { $HTTP["url"] =~ "^/myapp/" { url.rewrite-once = ("^/myapp/(.*)" => "/newapp/$1") } $HTTP["url"] =~ "^/newapp/" { proxy.server = ( "" => ( "" => ("host" => "192.168.1.30"...


Only top voted, non community-wiki answers of a minimum length are eligible