Update nextcloud-whitelist.yaml for no bans on dav file sync.

[UnknownHiker]

HTTP 200 needs to be whitelisted too for file-sync via webdav, as mentioned in Issue #669.

[mael2]

I also have issues with the nexcloud whitelist
i've created my own whitelist with this content:

name: crowdsecurity/zwhitelist
description: "Nextcloud Whitelist"
whitelist:
reason: "Joplin and Calendar"
expression:
- "evt.Parsed.request contains '/remote.php/dav' && evt.Parsed.file_ext == '.md'"
- "evt.Meta.http_status == '404' && evt.Parsed.request contains '/remote.php/dav/calendars'"

[UnknownHiker]

I also have issues with the nexcloud whitelist i've created my own whitelist with this content:

name: crowdsecurity/zwhitelist description: "Nextcloud Whitelist" whitelist: reason: "Joplin and Calendar" expression: - "evt.Parsed.request contains '/remote.php/dav' && evt.Parsed.file_ext == '.md'" - "evt.Meta.http_status == '404' && evt.Parsed.request contains '/remote.php/dav/calendars'"

Isnt that something you would like to put into the issue or create another pull request for? ;)

[LaurenceJJones]

I also have issues with the nexcloud whitelist i've created my own whitelist with this content:
name: crowdsecurity/zwhitelist description: "Nextcloud Whitelist" whitelist: reason: "Joplin and Calendar" expression: - "evt.Parsed.request contains '/remote.php/dav' && evt.Parsed.file_ext == '.md'" - "evt.Meta.http_status == '404' && evt.Parsed.request contains '/remote.php/dav/calendars'"

Isnt that something you would like to put into the issue or create another pull request for? ;)

Yes @mael2 if you want to push another fix you need to open a separate PR