Sal , avatar

Yeah, it looks to me like an nginx redirect of the kbinbot user-agent. For example, I’ve added the following block to my instance’s nginx config:

<pre style="background-color:#ffffff;">
<span style="color:#323232;">if ($http_user_agent ~* (testblock|megablock)) {
</span><span style="color:#323232;">        return 403;
</span><span style="color:#323232;">    }

You can now get the same response using:

curl -I --user-agent “testblock”

I wouldn’t want to jump ahead and assume some malicious or sneaky reason. The user agent could have been accidentally lumped into a block list during a DDoS mitigation strategy, or they could have run into some unexpected issues when upgrading to 0.18.0 and they thought this might be a quick temporary fix while patching - but patching is taking them longer than expected. I don’t know, but it is a curious observation.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • tech
  • insurance
  • testing
  • drbboard
  • updates
  • til
  • programming
  • bitcoincash
  • marketreserach
  • wanderlust
  • Sacramento
  • All magazines