Skip to content
This repository was archived by the owner on Jan 19, 2019. It is now read-only.
This repository was archived by the owner on Jan 19, 2019. It is now read-only.

Changes to location regexp broke previously working configs #39

@kscherer

Description

@kscherer

Prior to commit 2379d2d I had the following:

  SERVER1REVERSE_PROXY_LOCATION1: "/"
  SERVER1REVERSE_PROXY_PASS1: "http://layerindex:5000/"
  SERVER1REVERSE_PROXY_APPLICATION1: "custom"
  SERVER1REVERSE_PROXY_HEADER1FIELD1: 'Host $$http_host'
  SERVER1REVERSE_PROXY_HEADER1FIELD2: 'X-Forwarded-For $$proxy_add_x_forwarded_for'
  SERVER1REVERSE_PROXY_HEADER1FIELD3: 'X-Forwarded-Host $$host'
  SERVER1REVERSE_PROXY_HEADER1FIELD4: 'X-Forwarded-Proto $$scheme'
  SERVER1REVERSE_PROXY_DIRECTIVE1FIELD1: 'proxy_redirect off'

which created the following config:

    location / {
      proxy_pass http://layerindex:5000/;
      proxy_set_header Host $http_host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Host $host;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_redirect off;
    }

After the commit the config looks like this:

    location ~* ^/(.*) {
      set $backend "http://layerindex:5000/";
      proxy_pass $backend$1$is_args$args;
      proxy_set_header Host $http_host;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Host $host;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_redirect off;
    }

The only way to make it work was to add:

SERVER1REVERSE_PROXY_DISABLE_RESOLVER1: "true"

to revert this behavior. What am I missing? Why was the default behavior changed? A notification about breaking changes would have been much appreciated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions