This seems like you're running an nginx reverse proxy, and trying to allow it to work with a specific prefix.

So rather than:

• http://blah.example.com/

You're expecting visitors to use:

• http://blah.example.com/puppet-dashboard/

Is that correct? So in your case you'd add /puppet-dashboard as the URL-prefix. (Or even the full http://blah.example.com/puppet-dashboard ).

If so I think this pull-request would solve the problem, but it is not the correct approach. I'd update the nginx configuration to handle the prefix. Something like:

server {
    listen 80 default;
    server_name blah.example.com;

    rewrite ^/puppet-dashboard(.*)$ /$1 break;

   location / {
       allow all;

          proxy_pass http://127.0.0.1:1243;
          proxy_set_header Host $host;
          proxy_set_header X-Real-IP $remote_addr;
          proxy_set_header X-Scheme $scheme;
          proxy_connect_timeout 30;
          proxy_send_timeout 3600;
          proxy_read_timeout 3600;
          send_timeout 3600;
      }
  }

Am I missing something, or misunderstanding your use-case?

So I do use proxy_pass to get the service behind nginx (need port 443 and valid cert) under a /puppet prefix. The issue I ran into is that all of the links are hard coded to use / instead of a relative path. As a result the main report page works (minus the tablesort JS), but no links work inside of that without doing an html rewrite on the outbound html.

So example workflow from my running server:

• load /puppet/ and see report page
• click on $fqdn and html links to /puppet/node/$fqdn
• nginx proxies that as /node/$fqdn to the Go service
• service returns node view as expected

So it all work correctly because the html has the correct path for the proxy prefix.

Now I understand, thank-you. I was going to suggest using relative-links instead, to avoid having to add a new configuration option, but it seems that gets annoying pretty quickly.

(i.e. I could change /report/123 to report/123, and similar for the node-view. But having the header link to / is a problem.)

I'll read your PR this evening/tomorrow and if there are no obviously problems I'll merge then.

Thanks for your explanation, and your contribution :)

This took longer than expected; but I'll merge now and cleanup soon.

Thanks again for your contribution :)