-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[File Firewall] If you deleted the rules is not deleted on the Desktop #4071
Comments
Logs
|
@nickvergessen @ckamm @ogoffart @dragotin Maybe the file firewall's actions should not be blacklisted? @Dianafg76 If it says |
This is the whole point of the blacklist. |
related #3490 |
The blacklist is mostly a "don't annoy users" thing. Syncing would mostly work better without it, but we'd also bother users more. Blacklisting file firewall errors means that, if the firewall rules change, it can take up to a day (max blacklist time) for a file that previously failed due to the firewall to be retried. Maybe it'd be beneficial to just mute the error instead of not even trying files that are blacklisted? The main drawback would be retrying costly uploads more often. |
The goal is to also avoid unecessary traffic. In practice I would not expect the rules to be changed that often anyway. But maybe 1 day is too much and we should limit to a couple of hours? |
Well, since the firewall has an option to block timebased, hourly sounds way better than 1 day. |
Well firewall will use that header in 9.0, for 8.2 that's not possible due to the architecture. |
@nickvergessen Is |
@Dianafg76 Note that the symptoms will still be the same. But the client will now retry a previous firewall-related error after 1h or less (instead of 1 day). |
Response as of 9.0 is: <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:o="http://owncloud.org/ns">
<s:exception>OCA\DAV\Connector\Sabre\Exception\Forbidden</s:exception>
<s:message>Access to this resource has been forbidden by a file firewall rule.</s:message>
<o:retry xmlns:o="o:">true</o:retry>
<o:reason xmlns:o="o:">Access to this resource has been forbidden by a file firewall rule.</o:reason>
</d:error> In 8.2 I think it's something like: <d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:o="http://owncloud.org/ns">
<s:exception>OCP\SabrePluginException</s:exception>
<s:message>Access to this resource has been forbidden by a file firewall rule.</s:message>
</d:error> So yes the message should contain the f*** word |
Note that the server is i18n'ed |
@guruz @nickvergessen Then it won't work. I think it would be safe to do this for 403s generally. |
Currently 403 is only used for this case, so yes sounds save |
We can't detect firewall errors due to error message localization.
I tested this issue, and is working ok |
Steps to reproduce
Expected behaviour
The rule should disappear
Actual behaviour
When sync is complete, the rules remain on the Desktop
Server configuration
Desktop v ownCloud-2.1.0.2851-nightly20151104.pkg
Server v {"installed":true,"maintenance":false,"version":"8.2.0.12","versionstring":"8.2.0","edition":"Enterprise"}
The text was updated successfully, but these errors were encountered: