On Monday, 9 July 2018 11:27:58 MSK Gena Makhomed wrote: > On 09.07.2018 10:41, Sergey Budnevitch wrote: > > >> https://hg.nginx.org/nginx/atom-log > >> https://hg.nginx.org/pkg-oss/atom-log > >> https://hg.nginx.org/nginx.org/atom-log > >> > >> stop working, instead of RSS feed html+javascript returned. > >> RSSOwl can't execute javascript and don't see these RSS feeds. > >> > >> Also I can't download http://hg.nginx.org/nginx/archive/tip.tar.gz > >> with curl - also html+javascript returned, which curl don't understand. > >> > >> can you please fix these issues? > > > atom-tags, atom-log, archive were removed from bot mitigation mechanism > > thank you! but issue not fixed for these urls: > > http://hg.nginx.org/pkg-oss/atom-log > https://hg.nginx.org/pkg-oss/atom-log > > http://hg.nginx.org/nginx.org/atom-log > https://hg.nginx.org/nginx.org/atom-log > > - they still return html+javascript. > > P.S. > > bot mitigation mechanism written as custom "C" module > or written using only njs, without 3rd party modules? >
It's pretty easy to write one using only njs. > it is closed source code or will be open source code? > > bot mitigation mechanism via javascript good for bots, > but it also disables site indexing by search engines.(?) > > it will be good to whitelist search engines by DNS, > at least main search engines: Google, Yandex and Bing. [..] All main search engines are able to run JS. Nowadays there're a lot of JS-only sites. wbr, Valentin V. Bartenev _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel
