HTTP site hosted behind HTTPS proxy not using correct protocol when generating sitemap
So I have an interesting set up which is affecting the XML site map generation
Our web site is hosted behind a proxy server which holds the sites SSL certificate.
So the site sits native in HTTP, but the outside world sees it as HTTPS because of the proxy.
When the sitemap is generated, it looks like the because the site is in HTTP, all links in the sitemap are generated by the IIS domain inside the proxy, ie the HTTP.
This obviously causes some issues because all the links are actually HTTPS in the outside world
Is there anyway to force the sitemap generation to use a specific domain ?
It takes the scheme of the request that comes in so that makes sense. There was always a way to override this on node level but now I have made a config option that you can use to force HTTPS rendering. Add the following snippet to the appsettings of Web.config and all rendering of the sitemap should be https:
2.2.4 will also be release. 2.8 is Umbraco V8+ only. Can't support both Umbraco versions in a single package. Will do some final testing on 2.2.4 before release in the coming week(s)
SEOChecker takes the scheme from the HTTPRequest which is propably http instead of https. In V8 version I am about to release this is addressed but heavily using on Umbraco V8 architecture so not easy to backport to V7. If you can make sure scheme is always https it will work.
HTTP site hosted behind HTTPS proxy not using correct protocol when generating sitemap
So I have an interesting set up which is affecting the XML site map generation
Our web site is hosted behind a proxy server which holds the sites SSL certificate.
So the site sits native in HTTP, but the outside world sees it as HTTPS because of the proxy.
When the sitemap is generated, it looks like the because the site is in HTTP, all links in the sitemap are generated by the IIS domain inside the proxy, ie the HTTP.
This obviously causes some issues because all the links are actually HTTPS in the outside world
Is there anyway to force the sitemap generation to use a specific domain ?
Hi,
It takes the scheme of the request that comes in so that makes sense. There was always a way to override this on node level but now I have made a config option that you can use to force HTTPS rendering. Add the following snippet to the appsettings of Web.config and all rendering of the sitemap should be https:
Download 2.2.4 Hotfix here. Will be included in the 2.2.4 release.
Domain can be set when you assign the canonical domain to a rootnode
Best,
Richard
Thanks Richard, much appreciated!
Hi Richard, see you updated to 2.8, does that mean the 2.2.4 (for Umbraco 7) is not coming now?
2.2.4 will also be release. 2.8 is Umbraco V8+ only. Can't support both Umbraco versions in a single package. Will do some final testing on 2.2.4 before release in the coming week(s)
Thanks Richard, looking forward to it
Hi Richard
I have some issue with a site behind a HTTPS proxy.
Running Umbraco 7.15.6 and seochecker 2.2.5.
The 404 are not working it just gives the default umbraco 404 page
Sitemap give a 504 Gateway Time-out - The server didn't respond in time.
I have tried to add didn't do anything..
SEOChecker takes the scheme from the HTTPRequest which is propably http instead of https. In V8 version I am about to release this is addressed but heavily using on Umbraco V8 architecture so not easy to backport to V7. If you can make sure scheme is always https it will work.
Hope this helps,
Richard
Hey Thanks :)
Not quite sure about what you mean here "If you can make sure scheme is always https it will work."
The solution is set to umbracoUseSSL = false ?
No mean that behind the proxy all requests need to be https as well.
Hmm okay. It's not possible. All the certificates are handled by the haproxy infront of the load balancer
Is there a way to force it to use https ?
I have added ?
For V8 that will be possible soon indeed as mentioned above yesterday.
is working on a reply...