ProxyPass

(coming soon) Integrating Nearest! into your website structure

If you need to integrated Nearest! into the main navigation of your website (mycompany.com/locations) a ProxyPass connection needs to be added to your web-server configuration. In this case external traffic will be encrypted by your host-systems ssl certificate. Internal traffic will be encrypted with the certificate provided by Nearest!.

Changes to the webserver configuration can lead to unavailability of the entire server and should only be performed by system administrators or devops.

Nginx

server {
    listen mycompany.com:80;
    server_name  mycompany.com;
    ...
    location /locations/ {
        proxy_set_header X-Forwarded-Host $host:$server_port;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_pass https://yourapp.nearest.place/;
    }
}

Apache

<VirtualHost mycompany.com:80>
  ServerName mycompany.com
  ...
  ProxyPass /locations/ https://yourapp.nearest.place/
  ProxyPassReverse /locations/ https://yourapp.nearest.place/
</VirtualHost>