Re: http://common-lisp.net is unavailable

Anton Vodonosov <[email protected]>
Newsgroups gmane.lisp.common-lisp-net.devel
Message-ID <[email protected]>
Yes.

I've been using http://trac.common-lisp.net/cl-openid/ from browser.

At the same time I've been doign

darcs clone http://common-lisp.net/project/cl-openid/darcs/cl-openid/

It fails in the middle, because I think every darcs repositories expose

every patch as a separate HTTP resource, or something like that.

(Anyway, later I found that repo clone on my old hard drive and acomplished

my goal, which was to migrate cl-open-id source code to github)

And also I've decided to fix some failed cl-open-id tests, and so was running

the test sutie. That test suite needs to fetch some HTTP resources,

and the author chosen several common-lisp.net resources.

Nothing massive, Ive traced drakma:http-request, just 7 HTTP requests

to common-lisp.net. Only 1 more than the limit :)

05.09.2014, 12:49, "Erik Huelsmann" <[email protected]>:

Hi Anton,

To reduce the effect of malicious bots, I've set a connection limit of 6/min. Normal browsers don't have any issues with this, due to the fact that they open one tcp/ip connection and use that to pipeline the HTTP requests. Maybe you're doing something that hits this limit?

Regards,

Erik.

On Fri, Sep 5, 2014 at 5:07 AM, Anton Vodonosov <[email protected] > wrote:

More precisely: it is sometimes available, sometimes not available.

The impression as if some connection limit is being exhausted.
Maybe bots crawl it again?

_______________________________________________
Clo-devel mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/clo-devel

--

Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.

Robust and Flexible. No vendor lock-in.

_______________________________________________
Clo-devel mailing list
[email protected]
http://common-lisp.net/cgi-bin/mailman/listinfo/clo-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.