On a Azure-hosted site (although the same would probably in most environments other than dedicated single-IIS hosts), the understandably doesn't resolve.
Should it use the configured umbracoApplicationUrl ?
It will get the hostname from httpcontext. If that containts localhost it will return that. I assume this is related to the other issue you mentioned earlier? That will be done in the 2.10 release.
This happens to be in the same load-balanced Azure webapp that I was asking about database configuration, but a different issue.
So SEOChecker derives the hostname from the HttpContext of the first request presumably? I'm guessing that because we're using applicationInitialization, that's where localhost is getting captured in the first request. If there's any possibility of using the configured umbracoApplicationUrl, that would be great?
Frequent requests to localhost
We are seeing vast numbers of requests generated by SEOChecker to http://localhost/umbraco/seochecker/seocheckerscheduleapi/run
On a Azure-hosted site (although the same would probably in most environments other than dedicated single-IIS hosts), the understandably doesn't resolve.
Should it use the configured umbracoApplicationUrl ?
Using SEOChecker 2.9.1
Hi Phil,
It will get the hostname from httpcontext. If that containts localhost it will return that. I assume this is related to the other issue you mentioned earlier? That will be done in the 2.10 release.
Best,
Richard
This happens to be in the same load-balanced Azure webapp that I was asking about database configuration, but a different issue.
So SEOChecker derives the hostname from the HttpContext of the first request presumably? I'm guessing that because we're using
applicationInitialization, that's where localhost is getting captured in the first request. If there's any possibility of using the configuredumbracoApplicationUrl, that would be great?Phil
Hi Phil,
Will include that in 2.10 indeed.
Any update on this @Richard?
Hi Jeavon,
You can use the latest RC and set umbracoApplicationUrl then it will use that url instead of the one coming from a proxy.https://www.dropbox.com/s/eubnvrg46uxha18/seo-checker210_0.zip?dl=0
Hope this helps,
Richard
Thank you, any chance of a v7 version that includes this change? 😁
Can be done in future but this feature was Completely rebuilld in V8 using dependency injection is not a quick fix ...
That would be great as it currently floods the logs with this exception. I guess there's not an appsetting to manually set this already?
is working on a reply...