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 c22de5705c9463e15c0ccce623779b3d21c67ebb..b12cf7c1047f1e26b16a0cd28917ae1c81093a03 100644 (file)
--- 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++) {