llvm dev - Mar 2016 - LLVM.org/viewvc down?

Unfortunately, we had lot of bogus requests to viewvc (e.g. asking for
history / blame for random revision) which looked like a DoS. Most
probably we'll enable it after llvm.org will be migrated to new
hardware.

On Tue, Mar 15, 2016 at 1:24 PM, Hans Wennborg <hans at chromium.org>
wrote:
> The commit emails, including the ones in the mailing list archives,
> also have links to the viewvc, all of which are now broken.
>
> +1 for getting the viewvc back up, if at all possible.
>
> On Tue, Mar 15, 2016 at 7:41 AM, Yung, Douglas via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> Is there any eta for when viewvc will be back? I prefer to use viewvc
>> because all of the commit emails have the SVN commit number, but not
the
>> corresponding git hashes, so it makes it easier to look it up. Or is
there
>> some easy way to map an svn commit number to the corresponding git
hash?
>>
>>
>>
>> Douglas Yung
>>
>>
>>
>> From: Johan Engelen [mailto:jbc.engelen at gmail.com]
>> Sent: Saturday, March 12, 2016 5:03 AM
>> To: Anton Korobeynikov
>> Cc: Yung, Douglas; llvm-dev at lists.llvm.org
>> Subject: Re: [llvm-dev] LLVM.org/viewvc down?
>>
>>
>>
>> On Sat, Feb 27, 2016 at 12:14 PM, Anton Korobeynikov via llvm-dev
>> <llvm-dev at lists.llvm.org> wrote:
>>
>> It's currently disabled until the issues with llvm.org load would
be
>> resolved. Use klaus instead.
>>
>>
>>
>> Thanks for mentioning "klaus", I did not know about it
before. Perhaps a
>> link to it can be added on llvm.org? (next to ViewVC)
>>
>>
>>
>> Regards,
>>
>>  Johan Engelen
>>
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>


-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University

On 15 Mar 2016, at 12:42, Anton Korobeynikov via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Unfortunately, we had lot of bogus requests to viewvc (e.g. asking for
> history / blame for random revision) which looked like a DoS. Most
> probably we'll enable it after llvm.org will be migrated to new
> hardware.
Can we just disable / limit these features?  I gave up trying to use viewvc to
show me revision logs a while ago because it would just sit there for ages and
eventually the request would time out.  It doesn’t seem to cache any of this
data and it’s very expensive to get from svn.

David

On Tue, Mar 15, 2016 at 03:42:45PM +0300, Anton Korobeynikov via llvm-dev
wrote:
> Unfortunately, we had lot of bogus requests to viewvc (e.g. asking for
> history / blame for random revision) which looked like a DoS. Most
> probably we'll enable it after llvm.org will be migrated to new
> hardware.
How much of that are stupid (chinese) spiders? I had a lot of load
issues for the NetBSD fossil repositories until I added the following to
my nginx configuration:

  if ($http_user_agent ~*
(360Spider|80legs|App3leWebKit|Baiduspider|EasouSpider)) {
    return 403;
  }

Joerg

> How much of that are stupid (chinese) spiders?
You're right, the majority of them were from Chinese IPs.
> I had a lot of load
> issues for the NetBSD fossil repositories until I added the following to
> my nginx configuration:
>
>   if ($http_user_agent ~*
(360Spider|80legs|App3leWebKit|Baiduspider|EasouSpider)) {
>     return 403;
>   }
I saw some other user agents as well. And they ignored robots.txt, yes.

-- 
With best regards, Anton Korobeynikov
Faculty of Mathematics and Mechanics, Saint Petersburg State University