Crawler Check

  • Resolved aaronwp03

    (@aaronwp03)


    1 year, 11 months ago

    Hello, would like to get your opinion on this:

    Report number: ABXICUKK

    Report date: 04/08/2023 12:47:37

    1. Every time I run a manual crawl, it always results in blue. That does mean I am not caching properly because I haven’t had a green result even once. I noticed, my pages only get fast after the third visit. Then after 5 minutes, if I visit the same page again – it feels like a first visit because it has to load for a while. https://prnt.sc/ZozW0Gkzx9NJ
    2. For the Watch Status, can this be interpreted as working? https://prnt.sc/H_4wXpVGtE_J

    There’s only position 1 but I have lots of links to crawl. I saw some examples and I see positions 27, 5, etc. Is position means URL?

    3. This is the result I get as well. All blue and there are 404 and 403: https://prnt.sc/ADyByHmTsNgg

    Thank you.

Viewing 3 replies - 16 through 18 (of 18 total)
  • Plugin Support qtwrk

    (@qtwrk)

     X-LiteSpeed-Cache-Control: private,max-age=1800

    the page is cached privately for login user , but as you can see in log , it has short TTL , so it expires soon

    Thread Starter aaronwp03

    (@aaronwp03)

    Yes. It expires every 30 minutes. But the problem is, if I open the page the first time, it isn’t cached. Then the second time, it isn’t cached, the third time it is cached because it’s fast. If I close the app, and open the page again – it isn’t cached again, open the second time, isn’t cached, third time now it’s fast. This is not the case with Google chrome, they are cached right away
    This is within 5 minutes of testing, not even 30 minutes.

    What about line 49? It says;

    9 => ‘Cache-Control: no-cache, must-revalidate, max-age=0’,

    Plugin Support qtwrk

    (@qtwrk)

    no , that’s normal , that’s for browser , nothing to do with plugin

    then you need to obtain the log for all these steps you have mentioned

    but it is common some plugin will do a purge all for private cache upon login action

    and in your case , it appears there are 2 vary change action from the log , these could lead the initial request or even 2nd request giving cache miss

    but please try the log , the log will tell

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Crawler Check’ is closed to new replies.

Tags