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

Expand S3 protocol to accept 204 No Content as File not Found #1695

Closed
bari12 opened this issue Oct 23, 2018 · 0 comments
Closed

Expand S3 protocol to accept 204 No Content as File not Found #1695

bari12 opened this issue Oct 23, 2018 · 0 comments
Assignees

Comments

@bari12
Copy link
Member

bari12 commented Oct 23, 2018

Motivation

Some S3 storage report 204 No Content if a file does not exist instead of 404 which creates error reports in Rucio. Expand the protocol to also interpret the 204 as a non existing file.

@bari12 bari12 removed their assignment Jan 23, 2019
TomasJavurek added a commit to TomasJavurek/rucio that referenced this issue Jan 8, 2020
bari12 added a commit that referenced this issue Jan 9, 2020
…r_204_status_code

Protocol: expanding s3 protocol for 204 error code - #1695
bari12 added a commit that referenced this issue Jan 9, 2020
…r_204_status_code

Protocol: expanding s3 protocol for 204 error code - #1695
@bari12 bari12 added this to the 1.21.5-clients milestone Jan 9, 2020
@bari12 bari12 closed this as completed Jan 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants