[ceph-users] radosgw with nginx

[Erdem Agaoglu]

Hi all,

We are trying to run radosgw with nginx.
We've found an example https://gist.github.com/guilhem/4964818
And changed our nginx.conf like below:

http {
    server {
        listen 0.0.0.0:80 <http://0.0.0.0/>;
        server_name _;
        access_log  off;
        location / {
            fastcgi_pass_header Authorization;
            fastcgi_pass_request_headers on;
            include fastcgi_params;
            fastcgi_keep_conn on;
            fastcgi_pass unix:/tmp/radosgw.sock;
        }
    }
}

But the simplest test gives following error:

# curl -v http://x.x.x.x/bucket/test.jpg
* About to connect() to x.x.x.x port 80 (#0)
*   Trying x.x.x.x ... connected
> GET /bucket/test.jpg HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: x.x.x.x
> Accept: */*
>
< HTTP/1.1 400
< Server: nginx/1.1.19
< Date: Thu, 23 May 2013 15:34:05 GMT
< Content-Type: application/json
< Content-Length: 26
< Connection: keep-alive
< Accept-Ranges: bytes
<
* Connection #0 to host x.x.x.x left intact
* Closing connection #0
{"Code":"InvalidArgument"}

radosgw logs show these:

2013-05-23 08:34:31.074037 7f0739c33780 20 enqueued request req=0x1e78870
2013-05-23 08:34:31.074044 7f0739c33780 20 RGWWQ:
2013-05-23 08:34:31.074045 7f0739c33780 20 req: 0x1e78870
2013-05-23 08:34:31.074047 7f0739c33780 10 allocated request req=0x1ec6490
2013-05-23 08:34:31.074084 7f0720ce8700 20 dequeued request req=0x1e78870
2013-05-23 08:34:31.074093 7f0720ce8700 20 RGWWQ: empty
2013-05-23 08:34:31.074098 7f0720ce8700  1 ====== starting new request
req=0x1e78870 =====
2013-05-23 08:34:31.074140 7f0720ce8700  2 req 4:0.000042::::initializing
2013-05-23 08:34:31.074174 7f0720ce8700  5 nothing to log for operation
2013-05-23 08:34:31.074178 7f0720ce8700  2 req 4:0.000080::GET
/bucket/test.jpg::http status=400
2013-05-23 08:34:31.074192 7f0720ce8700  1 ====== req done req=0x1e78870
http_status=400 ======


Normally we expect a well formed 403 (because request doesn't have
Authorization header) but we have a 400 and cannot figure out why.

Thanks in advance.

-- 
erdem agaoglu

_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com