block bots using http bearer auth
Find a file
2026-09-08 19:13:17 +02:00
example.service initial commit 2026-09-08 18:36:12 +02:00
tool initial commit 2026-09-08 18:36:12 +02:00
.gitattributes initial commit 2026-09-08 18:36:12 +02:00
.gitignore initial commit 2026-09-08 18:36:12 +02:00
check_token.c initial commit 2026-09-08 18:36:12 +02:00
example.input initial commit 2026-09-08 18:36:12 +02:00
meson.build initial commit 2026-09-08 18:36:12 +02:00
meson.options initial commit 2026-09-08 18:36:12 +02:00
nobotgate-access.c initial commit 2026-09-08 18:36:12 +02:00
nobotgate.c initial commit 2026-09-08 18:36:12 +02:00
nobotgate.h initial commit 2026-09-08 18:36:12 +02:00
parse_token.c make header field names case insensitive 2026-09-08 19:13:17 +02:00
README initial commit 2026-09-08 18:36:12 +02:00
send_headers.c initial commit 2026-09-08 18:36:12 +02:00

nobotgate
=========

When you run a private site (that still uses a
super-serve), you can use nobotgate to require users to
provide an http bearer token. This way, bots won't flood
your site with spam.

usage
-----

use nobotgate(1) together with a super-server such as inetd(8),
tcpserver(1) or s6-tcpserver:
  # tcpserver 0.0.0.0 80 nobotgate /etc/wwwtokens ./on-valid ./on-invalid
where /etc/wwwtokens contains:

and ./on-valid contains:
  #!/bin/sh
  exec busybox httpd -i -h /var/www
and ./on-invalid contains:
  #!/bin/sh
  exec nobotgate-access cat usage
and usage contains:
  No bearer token specified!