- Issue created by @mlahde
- 🇫🇮Finland mlahde
This patch works for us, but is far from stylish. Prolly the setting of the actual port should be somewhere else.
I'd be interested to know if anybody else has been facing this, and how did you tackle it? I'm still trying to get this in the server side, so this is probably a temporary solution. Yeah, right.
Usedgit diff origin/8.x-3.x > force-server-port-3468089-2.patch
- 🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU
I believe this is a duplicate of 💬 Force HTTPS for ACS and SLS Closed: works as designed .
There's a pointer in the samlauth README now, and a pointer to the Drupal documentation page https://www.drupal.org/node/425990 → .
I believe configuring these 'reverse_proxy ' settings is better than solving things in the samlauth module, because 'Drupal thinks the site is on a wrong port/protocol' affects more than just SAML. It's a general Drupal issue.
If you can't make it work, then I am open to discussing this (like in 💬 How to resolve wrong protocol issue (reverse proxies with dynamic IP)) Needs work ), but I need specific info on why it would not be working. Until further notice I believe you're getting the port/protocol info in some proxy headers that Drupal can pick out,
If you have suggestions to improve the README to make this more obvious, I'm open to them.
The Drupal documentation page really needs an overhaul / to be more prominently featured. Realistically... that's not likely to make it to the top of my to-do list.