PhilippC / PhilippC/keepass2android
[FEAT] add to FAQ: nginx bot protection might block access to kdbx file on WebDAV share
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.2k
- Forks
- 478
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 2
Description
you might want to link to https://forum.opnsense.org/index.php?topic=27332.15 in the FAQ
It costed me some more gray hairs to find out that the nginx reverse proxy of an OPNsense has a list of bot user agents that includes keepass2androids "okhttp".
It get's nasty when the default setting for "log banned requests" is off!
So if you get an 403 error when trying to access a kdbx on a webDAV share, have a look at the bot protection settings of your webserver/reverse proxy.
And make sure that the logging of such requests is in a state you have in mind.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the project's FAQ and review the existing entries for WebDAV access and HTTP 403 errors. Add a link to the referenced forum discussion with the nginx bot-protection and logging explanation, then confirm the FAQ clearly explains what users should check when a kdbx file is blocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, nginx
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100