Skip to content
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

[duplicate] Optional checksumming #8

Closed
cybic opened this issue Apr 17, 2013 · 1 comment
Closed

[duplicate] Optional checksumming #8

cybic opened this issue Apr 17, 2013 · 1 comment

Comments

@cybic
Copy link

cybic commented Apr 17, 2013

The client should be allowed to send a header indicating which checksum algorithms it accepts, and the server should optionally checksum each data chunk, allowing the client to resend on checksum error.

Something like an 'Accept-Checksum: md5,crc32', either in the initial POST or in each PUT, and a following Checksum header in the response to each data chunk. The checksum algo should be negotiated, but something like md5 should probably be recommended.

The client is in charge of deciding whether a resend is required.

@felixge
Copy link
Contributor

felixge commented Apr 17, 2013

#7 is already tracking this, so closing this as a duplicate.

Anyway, can you comment on #7 to give your feedback on whether or not this should be part of the core protocol?

@felixge felixge closed this as completed Apr 17, 2013
nerro added a commit to nerro/tus-resumable-upload-protocol that referenced this issue Aug 29, 2016
Server must ignore 'Tus-Resumable' header
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants