okhttp user agent is blocked in potential bot crawling lists #1992
-
Problem scope
App version
Android version and device/firmware typeNo response Steps to reproduce
Problem shouldn't be limited to Nextcloud and also shouldn't be limited to OPNsense Actual resultDAVx5 gets the response: 403 Nginx in OPNsense bans the request because by default it bans every request with user agent containing "okhttp". This is because it assumes that only bots use "okhttp" as user agent: Expected resultThe user agent of DAVx5 should not include "okhttp". Then the request would pass the Nginx proxy successfully. The same problem was fixed in the Home Assistant App. Seems like they modified their user agent string to avoid getting banned by OPNsense (or other services that include some lists of known bots and crawlers). You can find everything related to this topic in their Issue: home-assistant/android#1364 Further infoA temporary workaround is to remove "okhttp" from the OPnsense Nginx (--> Nginx --> Configuration --> General Settings --> Global HTTP Settings --> Bots User Agents) But then you have also allowed all bots with okhttp in their user agent. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
Why is it a DAVx5 bug if someone is blocking its user agent? However I wanted to rewrite the User-Agent anyway (and possibly remove okhttp). However I'm sure that this will break a lot of existing access rules. |
Beta Was this translation helpful? Give feedback.
Tracked in #1996