From: Javier M. Mellid <jmunhoz@igalia.com>
Date: Fri, 23 Oct 2015 09:09:18 +0000 (+0200)
Subject: rgw: achieve same error behaviour in S3 and RGW when processing signedheaders
X-Git-Tag: v10.1.0~351^2^2~16
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=4da853950cf6c266eb43232a55dffc91e5b32489;p=ceph.git

rgw: achieve same error behaviour in S3 and RGW when processing signedheaders

This patch gets the same error response in S3 and RGW when the error is related
to the signedheaders processing.

Fixes: #10333

Signed-off-by: Javier M. Mellid <jmunhoz@igalia.com>
---

diff --git a/src/rgw/rgw_rest_s3.cc b/src/rgw/rgw_rest_s3.cc
index c22de5705c94..b12cf7c1047f 100644
--- a/src/rgw/rgw_rest_s3.cc
+++ b/src/rgw/rgw_rest_s3.cc
@@ -3020,8 +3020,8 @@ int RGW_Auth_S3::authorize_v4(RGWRados *store, struct req_state *s)
     }
     const char *t = s->info.env->get(token_env.c_str());
     if (!t) {
-      dout(10) << "error getting env var" << dendl;
-      return -EINVAL;
+      dout(10) << "warning env var not available" << dendl;
+      continue;
     }
     if (token_env == "HTTP_CONTENT_MD5") {
       for (const char *p = t; *p; p++) {