Your browser is suspiciously forcing uncompressed replies

Your browser is suspiciously forcing uncompressed replies
You're probably reading this page because you've attempted to
access some part of my blog (Wandering
Thoughts) or CSpace, the wiki thing it's
part of. Unfortunately you're using a browser (or client library)
that my anti-crawler precautions consider suspicious because it's
forcing completely uncompressed replies in a suspicious way that
is a signature of high volume crawlers that are trying to deflect
gzip bombs. Specifically, your browser or client is advertising
one of the following Accept-Encoding values:

Accept-Encoding: identity
Accept-Encoding: identity;q=1, *;q=0
Accept-Encoding: gzip;q=0

Due to the ongoing problems with abusive high volume crawlers
using forged User-Agent values (apparently in part to gather data
for LLM training), those Accept-Encoding values are not normally
accepted.

If this is in error and you're using a current version of your
browser of choice, you can contact me at my current place at the
university (you should be able to work out the email address
from that). If possible, please let me know what browser you're
using and so on, ideally with its exact User-Agent string.
Chris Siebenmann, 2025-08-14

Your browser is suspiciously forcing uncompressed replies

Your browser is suspiciously forcing uncompressed replies
You're probably reading this page because you've attempted to
access some part of my blog (Wandering
Thoughts) or CSpace, the wiki thing it's
part of. Unfortunately you're using a browser (or client library)
that my anti-crawler precautions consider suspicious because it's
forcing completely uncompressed replies in a suspicious way that
is a signature of high volume crawlers that are trying to deflect
gzip bombs. Specifically, your browser or client is advertising
one of the following Accept-Encoding values:

Accept-Encoding: identity
Accept-Encoding: identity;q=1, *;q=0
Accept-Encoding: gzip;q=0

Due to the ongoing problems with abusive high volume crawlers
using forged User-Agent values (apparently in part to gather data
for LLM training), those Accept-Encoding values are not normally
accepted.

If this is in error and you're using a current version of your
browser of choice, you can contact me at my current place at the
university (you should be able to work out the email address
from that). If possible, please let me know what browser you're
using and so on, ideally with its exact User-Agent string.
Chris Siebenmann, 2025-08-14