You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using an incorrect password during account setup the error message "There was an invalid response to an authenticated webdav request" is shown instead of the correct "Access forbidden by...".
This regression is due to the new redirection handling. I added a new finishedWithError() slot and didn't realize networkError() may already have been emitted beforehand.
The text was updated successfully, but these errors were encountered:
The problem was that on network error the networkError() and
finishedWithError() signals both fired. To fix it, I collapse all
error handing into a slot triggered by finishedWithError().
I tested the redirection case and the invalid credentials case.
The problem was that on network error the networkError() and
finishedWithError() signals both fired. To fix it, I collapse all
error handing into a slot triggered by finishedWithError().
I tested the redirection case and the invalid credentials case.
When using an incorrect password during account setup the error message "There was an invalid response to an authenticated webdav request" is shown instead of the correct "Access forbidden by...".
This regression is due to the new redirection handling. I added a new finishedWithError() slot and didn't realize networkError() may already have been emitted beforehand.
The text was updated successfully, but these errors were encountered: