Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Phil Dye 147 posts 302 karma points
    Sep 24, 2020 @ 14:27
    Phil Dye
    0

    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

  • Richard Soeteman 3808 posts 11792 karma points MVP
    Sep 24, 2020 @ 15:23
    Richard Soeteman
    0

    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

  • Phil Dye 147 posts 302 karma points
    Sep 28, 2020 @ 08:42
    Phil Dye
    0

    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?

    Phil

  • Richard Soeteman 3808 posts 11792 karma points MVP
    Sep 28, 2020 @ 08:46
    Richard Soeteman
    1

    Hi Phil,

    Will include that in 2.10 indeed.

Please Sign in or register to post replies

Write your reply to:

Draft