Bug #5675: New rgw issues 301 redirect without Location header - rgw - Ceph

Actions

Copy link

Bug #5675

closed

New rgw issues 301 redirect without Location header

Added by Faidon Liambotis almost 11 years ago. Updated almost 11 years ago.

Status:

Resolved

Priority:

Immediate

Assignee:

Greg Farnum

Target version:

% Done:

Source:

Community (user)

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

On my upgraded rgw running wip-5655 (c0e77c91b6c39998ef4e19a726db87b66850cf2c), i.e. two commits ahead 921a4aac8a89850303233fe188998202e0ddfe0d (current next), I see the following:

On two different request patterns (HEAD requests to containers via Swift API, GET requests via S3 API) I see 301 redirects. 301 responses are enough to break my application, so it was a surprise already, but the worst part is that these 301 don't have a Location header at all, which is makes this an invalid HTTP message. Additionally, on S3 requests, I get Content-Type: application/xml but with no body.

I'm not sure what I should switch my URLs to and I see nothing relevant on the docs, so this has killed my cluster for all intents and purposes...