rgw/cloud-restore: Do not send internal headers to cloud-endpoint

While fetching object from the cloud-endpoint, we need not set headers
used internally within RGW. Some of these headers are resulting in
403 error for GET response while using PoINT S3 cloud service.

Signed-off-by: Soumya Koduri <skoduri@redhat.com>

diff --git a/src/rgw/driver/rados/rgw_lc_tier.cc b/src/rgw/driver/rados/rgw_lc_tier.cc
index b153a7b4a4201bac43e144f541f0af1503bc55c7..4954b943b5ab1f55041b0e23d34d1f7f116ae5a9 100644 (file)
--- a/src/rgw/driver/rados/rgw_lc_tier.cc
+++ b/src/rgw/driver/rados/rgw_lc_tier.cc
@@ -279,10 +279,6 @@ int rgw_cloud_tier_get_object(RGWLCCloudTierCtx& tier_ctx, bool head,
 
   /* init input connection */
   req_params.get_op = !head;
-  req_params.prepend_metadata = true;
-  req_params.rgwx_stat = true;
-  req_params.sync_manifest = true;
-  req_params.skip_decrypt = true;
   req_params.cb = (RGWHTTPStreamRWRequest::ReceiveCB *)cb;
 
   ldpp_dout(tier_ctx.dpp, 20) << __func__ << "(): fetching object from cloud bucket:" << dest_bucket << ", object: " << target_obj_name << dendl;