Project

General

Profile

Actions

Bug #13817

open

RGW does not send HTTP header

Added by Ian Babrou over 8 years ago. Updated over 7 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

ivan@myhost:~$ curl -v -H "x-auth-token: ABC" http://myhost:9064/swift/v1/docker-registry-v2/files/docker/registry/v2/repositories/myrepo/_uploads/08c55423-abde-4759-b674-98e8a14ca15e/data
* Hostname was NOT found in DNS cache
*   Trying 1.2.3.4...
* Connected to myhost (1.2.3.4) port 9064 (#0)
> GET /swift/v1/docker-registry-v2/files/docker/registry/v2/repositories/myrepo/_uploads/08c55423-abde-4759-b674-98e8a14ca15e/data HTTP/1.1
> User-Agent: curl/7.38.0
> Host: myhost:9064
> Accept: */*
> x-auth-token: ABC
>
Content-Length: 0
Date: Tue, 17 Nov 2015 10:49:58 GMT

* Connection #0 to host myhost left intact

nginx in front of this rgw rightfully complains:

upstream sent no valid HTTP/1.0 header while reading response header from upstream, client: 5.6.7.8, server: swift.mydomain, request: "GET /swift/v1/docker-registry-v2/files/docker/registry/v2/repositories/myrepo/_uploads/08c55423-abde-4759-b674-98e8a14ca15e/data HTTP/1.1", upstream: "http://1.2.3.4:9064/swift/v1/docker-registry-v2/files/docker/registry/v2/repositories/myrepo/_uploads/08c55423-abde-4759-b674-98e8a14ca15e/data", host: "swift.mydomain" 

This doesn't happen to all files, only to some of them.

ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43)

I moved files to the different directory for further investigation.

Actions

Also available in: Atom PDF