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.

Sign up for GitHub

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

Jump to bottom

Incorrect assumption that iRODS always uses MD5 checksums #17

Open
colin-nolan opened this issue Feb 27, 2018 · 0 comments
Open

Incorrect assumption that iRODS always uses MD5 checksums #17

colin-nolan opened this issue Feb 27, 2018 · 0 comments
Labels
bug

Comments

@colin-nolan
Copy link
Contributor 

The response will always include the ETag header with its value corresponding to the MD5 checksum of the data object cached by iRobot, as calculated by iRODS.

iRODS does not have to use MD5 checksums (by default, it actually uses SHA256).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@colin-nolan