• Resolved tandlauer

    (@tandlauer)


    Hello,
    Since yesterday, I have noticed that one of my pages only get status 301 when crawled. I tried the update the page, to clear the LS cache, but I can’t get rid of this 301 status, and the page is not cached. Can you help me on this please ?

    If I may, I have another question about Quic.cloud CDN crawling. How/what to configure to get a proper crawling on the CDN cache ? How to verify it is working ?

    Thanks
    Thomas

    Report number: UCNLKDHK

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    the page you provided gives 404 error , please verify.

    please do me a screenshot where you see the 301 , and a link of that 301

    No , QC currently doesn’t support crawler , so if you set crwler with your server IP , then cache will be stored on your server, if you didn’t set server IP for crawler, then it will be closest QC node to server will store the cache.

    Best regards,

    Thread Starter tandlauer

    (@tandlauer)

    HI,

    Oh, sorry I did a mistake when writing the URL, that’s why you got a 404 error.
    Well, I solved the 301 issue by recreating the page. Now it is ok, hope it stays like that.

    I don’t understand what you mean by “so if you set crawler with your server IP”. I read that on the documentation too, but I don’t understand where is this setting ? Where can you set or not crawler with the server IP ?

    Best regards

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    It’s in General -> server IP

    when you set server IP , then crawler will force itself to resolve to that IP

    e.g.

    let’s say you have 2 servers , server 1 with IP 111.111.111.111 acts like reverse proxy or load balancer in front , and server 2 with IP 222.222.222.222

    if you set IP to 222.222.222.222 , then crawler will directly crawl on the IP you set , instead of fetching from DNS record which is leads to 111.111.111.111

    Best regards,

    Thread Starter tandlauer

    (@tandlauer)

    HI,
    Ok, now I understand a bit better. Was not so clear that the General -> IP server setting was used another tab (the crawler).
    However I’m using a custom sitemap to crawl my different language directories, and the url is complete, so I was thinking the crawler was using the full page URL to do its things rather than an IP
    Best regards

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    this has nothing to do with custom sitemap or not

    the sitemap itself will remains same , this server IP setting just changes what server it connects to

    Best regards,

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Crawler status 301 on one page’ is closed to new replies.