in reply to Re^5: Unable to connect
in thread Unable to connect

At about 1210 UTC today (corresponding to 08:10 server time), I modified Super Search to disallow Anonymous Monk usage. This should be considered experimental and temporary, to see if/how it affects site responsiveness.

Replies are listed 'Best First'.
Re^7: Unable to connect
by karlgoethebier (Abbot) on Mar 24, 2025 at 20:01 UTC
[reply]

      Interesting, but I don't see any evidence that google is the origin of the large number of hits.

[reply]

        You wrote:

        I just did some log file messin', and found that there have been a huge number of hits on the site from the address range 66.249.64. to 66.249.79.

        And these are listed in the Googlebot ranges. Therefore, the evidence does suggest that the "huge number of hits" are down to the googlebot crawler.

        🦛

[reply]

        So now it is proven. Or we regard it as proven. Or the majority consider it proven - it doesn't matter. According to pure doctrine returning anything other than 200 should work - even 418. That's about what Google suggests at the given location. And writing them a nice little email would also have a certain entertainment value. Maybe then this nightmare with the non-existent performance will soon come to an end.

        «The Crux of the Biscuit is the Apostrophe»

[reply]
Re^7: Unable to connect
by choroba (Cardinal) on Mar 24, 2025 at 22:15 UTC
    Just a few minutes ago, I got "Unable to connect" when trying to refresh the RAT.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
[reply]
[d/l]

In Section Perl Monks Discussion