Current location - Quotes Website - Personality signature - Amazon S3 V4 signature verification error.
Amazon S3 V4 signature verification error.
The deployed ceph object store uses an RGW gateway compatible with Amazon s3, and accesses the object store through Amazon S3. For the high availability and load balance of the gateway, a layer of nginx proxy forwarding is added in front of RWG gateway.

? When nginx is added, the V4 signature will report that our calculated request signature does not match the signature provided by you. Please check your key and signing method. , but V2 signatures do not report errors.

? After opening the project debugging log, nginx log and RGW gateway log, it is finally found that the header parameter Host of the request received by RGW gateway is different from that sent by the client.

? There is a parameter setting proxy _ set _ header Host xxx for forwarding http requests in nginx. When we use nginx for forwarding in the following forms:

? Nginx uses IP-based forwarding by default, so the request header parameters received by the server become 127.0.0. 1:8080 and 127.0.0. 1:9000.

? The above client refers to the level before nginx, and the server refers to the level after nginx. If there is a multi-level proxy, it needs to be set. Maybe it's not nginx, but Haproxy or something.