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

rgw:swift use Civetweb ssl can not get right url #6408

merged 1 commit into from Nov 6, 2015


None yet
4 participants
Copy link

dwj192 commented Oct 28, 2015

Fixes: #13628

Signed-off-by: Weijun Duan

@ghost ghost added the rgw label Oct 28, 2015


This comment has been minimized.

Copy link
Contributor Author

dwj192 commented Oct 28, 2015

swift https use civetweb ssl:

$swift -A https://node112/auth/v1 -U keyuser:keyuser -K keyuser stat -v   --insecure
HTTPConnectionPool(host='node112', port=80): Max retries exceeded with url: /swift/v1 (Caused by <class 'socket.error'>: [Errno 111] Connection refused)

use curl test:

$curl -D- -H 'X-Auth-User: keyuser:keyuser' -H 'X-Auth-Key: keyuser' https://node112/auth/v1.0 -k
HTTP/1.1 204 No Content
  X-Storage-Url: http://node112:0/swift/v1
X-Storage-Token: AUTH_rgwtk0f0000006b6579757365723a6b657975736572d1ea7a56dcfb24c1ceda31560d09b31614b8a06aa79e3fb7922b86ab39d4e676b710acb0
   X-Auth-Token: AUTH_rgwtk0f0000006b6579757365723a6b657975736572d1ea7a56dcfb24c1ceda31560d09b31614b8a06aa79e3fb7922b86ab39d4e676b710acb0
   Content-type: application/json
 Content-Length: 0

It should return X-Storage-Url: https://node112/swift/v1

This led to swift use civetweb ssl unusable


host = node112
keyring = /etc/ceph/ceph.client.radosgw.keyring
log file = /var/log/radosgw/client.radosgw.gateway.log
#rgw frontends = civetweb port=80
rgw frontends = "civetweb port=443s ssl_certificate=/home/ceph/ssl/server.pem"
rgw dns name = node112
debug rgw = 30

fixed it:

$swift -A https://node112/auth/v1 -U keyuser:keyuser -K keyuser stat -v   --insecure
StorageURL: https://node112/swift/v1
    Auth Token: AUTH_rgwtk0f0000006b6579757365723a6b657975736572474736a0c1eea5583cd231567374b037cf2457cbf5086fe1b00d53fb43afbf1b8dc1f7b0
       Account: v1
    Containers: 2
       Objects: 6
         Bytes: 23750
   X-Timestamp: 1446019260.95809
X-Account-Bytes-Used-Actual: 24576
    X-Trans-Id: tx000000000000000000002-00563080bc-232e3-default
  Content-Type: text/plain; charset=utf-8
 Accept-Ranges: bytes

@liewegas liewegas added the bug fix label Oct 29, 2015

@dwj192 dwj192 force-pushed the dwj192:swift-civetweb-ssl branch from 96e40b3 to 1040744 Oct 30, 2015

rgw:swift use Civetweb ssl can not get right url
Fixes: #13628

Signed-off-by: Weijun Duan <>

@dwj192 dwj192 force-pushed the dwj192:swift-civetweb-ssl branch from 1040744 to e0fd540 Oct 30, 2015

@yehudasa yehudasa self-assigned this Nov 3, 2015

yehudasa added a commit that referenced this pull request Nov 6, 2015

Merge pull request #6408 from dwj192/swift-civetweb-ssl
rgw:swift use Civetweb ssl can not get right url

Reviewed-by: Yehuda Sadeh <>

@yehudasa yehudasa merged commit c601a80 into ceph:master Nov 6, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.