-
Notifications
You must be signed in to change notification settings - Fork 82
Containerized | Versioning | Return 405 for Get/Head Specific Delete-Marker #8369
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
Comments
2 tasks
This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed. |
This issue is stale and had no activity for too long - it will now be closed. |
vh05
added a commit
to vh05/noobaa-core
that referenced
this issue
Jan 29, 2025
If the specified version in the request is a delete marker the returned is 405 Method Not Allowed. Fixes: noobaa#8369 Signed-off-by: Vinayakswami Hariharmath <vharihar@redhat.com>
vh05
added a commit
to vh05/noobaa-core
that referenced
this issue
Jan 29, 2025
If the specified version in the request is a delete marker the returned is 405 Method Not Allowed. Fixes: noobaa#8369 Signed-off-by: Vinayakswami Hariharmath <vharihar@redhat.com>
vh05
added a commit
to vh05/noobaa-core
that referenced
this issue
Feb 4, 2025
If the specified version in the request is a delete marker the returned is 405 Method Not Allowed. Fixes: noobaa#8369 Signed-off-by: Vinayakswami Hariharmath <vharihar@redhat.com>
This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment info
Background
In PR #8338 added a fix in NSFS.
Since I added the mapping between RPC error and S3 error:
METHOD_NOT_ALLOWED: S3Error.MethodNotAllowed
it might be that we probably have this issue in containerized.Actual behavior
Expected behavior
Steps to reproduce
More information - Screenshots / Logs / Other output
If the specified version in the request is a delete marker, the response returns a 405 Method Not Allowed error and the Last-Modified: timestamp response header.
The text was updated successfully, but these errors were encountered: