blacklabelops-legacy / nginx

Dockerized Ready-To-Go Nginx Reverse Proxy. Let's encrypt Support!
MIT License
95 stars 41 forks source link

Symphony (Confluence collaborative editing) does not work anymore #41

Closed esciara closed 6 years ago

esciara commented 6 years ago

Hi,

New generated proxy settings do not work with Symphony (Confluence collaborative editing).

With:

    environment:
      - 'SERVER2REVERSE_PROXY_LOCATION1=/synchrony'
      - 'SERVER2REVERSE_PROXY_PASS1=http://confluence:8091'
      - 'SERVER2REVERSE_PROXY_APPLICATION1=confluence6'

The old proxy settings now generated were:

        location /synchrony {
           set $backend "http://confluence:8091";
           proxy_pass $backend$uri$is_args$args;
           proxy_set_header X-Forwarded-Host $host;
           proxy_set_header X-Forwarded-Server $host;
           proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
           proxy_http_version 1.1;
           proxy_set_header Upgrade $http_upgrade;
           proxy_set_header Connection "upgrade";
        }

Now the proxy settings generated are:

        location ~* ^/synchrony(.*) {
          set $backend "http://confluence:8091";
          set $path $1;
          if ($path != false) {
            proxy_pass $backend/$path$is_args$args;
          }
          if ($path = false) {
            proxy_pass $backend$is_args$args;
          }
          proxy_set_header X-Forwarded-Host $host;
          proxy_set_header X-Forwarded-Server $host;
          proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
          proxy_http_version 1.1;
          proxy_set_header Upgrade $http_upgrade;
          proxy_set_header Connection "upgrade";
        }

And Symphony does not work. Removing the following and replacing it with proxy_pass $backend$uri$is_args$args; makes it work again:

          set $path $1;
          if ($path != false) {
            proxy_pass $backend/$path$is_args$args;
          }
          if ($path = false) {
            proxy_pass $backend$is_args$args;
          }
esciara commented 6 years ago

traced back to 07667578b30ae01ee8ab85c94be0f54cccfb62d0

blacklabelops commented 6 years ago

You can disable the new resolver: SERVER2REVERSE_PROXY_DISABLE_RESOLVER1=true