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
Cyberduck nicely prompts when it detects that the user is going to override a file. However, after confirming the client does not send the "Overwrite: T" header. The server is required to return 412 in this case I believe.
The text was updated successfully, but these errors were encountered:
This seems to fix it. If you want to explicitly track whether the user has hit "overwrite" I suppose that would go in the TransferOptions, but that's not passed down this far.
The Overwrite header is only specified for COPY and MOVE methods in RFC 2518. PUT is part of standard HTTP and always overwrites the resource from my understanding.
Cyberduck nicely prompts when it detects that the user is going to override a file. However, after confirming the client does not send the "Overwrite: T" header. The server is required to return 412 in this case I believe.
The text was updated successfully, but these errors were encountered: