Make this work behind https frontend proxy

[giggls]

Hello,

these changes might close #109. These 3 commits are how we got this to work behind an nginx frontend proxy and have apache listening on a selectable port (not hardcoded to 80).

However, we did not test if it still works without the frontend proxy.

Regards

Sven

[wheelybird]

Hi. The port Apache listens on shouldn't need to change as it's up to Docker to map the host port to the container port.
Some of the changes you made would generate invalid URLs as the root path would be duplicated.
With regards to the cookies, did you try using this container: wheelybird/ldap-user-manager:oldcookies?
I still haven't been able to reproduce the cookie issues on any browsers I use, even when using Nginx as a reverse proxy. I suspect the issue lies in the Nginx configuration or version that people are using.

[giggls]

The reason I need to map the port away from 80 is because I need to run docker in network=host mode in my use-case.

Your oldcookies container does work as far as the login is concerned but the SERVER_PATH stuff needed further patching.

To reflect these 3 things we made 3 commits.

As I already wrote this is untested with the default SERVER_PATH=/ setting.

Regards

Sven

[mstup]

Hey @wheelybird
Looks like I been faced with the some similar issue on work from behind of proxy.
I have couple issues which blocked me with final decision about wheelybird/ldap-user-manager:v1.11

For LogIn

1. I have Nginx proxy configured to open wheelybird on path myhost/ldap. No problem with this, initial page in opens and I can enter username and password.
   

2. But after click on LogIn button the next page is lost prefix "/ldap" and tried to open root path.
   

Here how LogIn traffic looks like:

For Groups

The same path prefix lost is on attempt to save new Group.

Group management page opens fine.

But on final step when click on Save button, the prefix /ldap is lost