You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using iamlive with proxy mode, when trying to upload object to s3 bucket getting:
An error occurred (NotImplemented) when calling the PutObject operation: A header you provided implies functionality that is not implemented
Error code is 501 NotImplemented.
How to reproduce?
Normal proxy iamlive setup
run aws s3 cp command into a bucket with empty file
What have you tried to do?
I tried to compare the list of headers between the proxy outputs to the aws cli with --debug , overall the headers seems to be the same.
Can confirm content-length exists, the only header that was in the proxy but not in the aws cli is Accept-Encoding but it seems to be coming from the goProxy, and I saw we're not deleting it.
I also tried to run other PUT method calls like create bucket with proxy, no issues there, just when trying to upload uploads into the bucket.
Note
When trying to upload a non-empty file with the same method above (aws cli), facing different issue where it can't connect to the proxy:
Failed to connect to proxy URL: "http://127.0.0.1:10080"
The text was updated successfully, but these errors were encountered:
What is the issue?
When using iamlive with proxy mode, when trying to upload object to s3 bucket getting:
Error code is 501 NotImplemented.
How to reproduce?
aws s3 cp
command into a bucket with empty fileWhat have you tried to do?
I tried to compare the list of headers between the proxy outputs to the aws cli with
--debug
, overall the headers seems to be the same.Can confirm content-length exists, the only header that was in the proxy but not in the aws cli is
Accept-Encoding
but it seems to be coming from the goProxy, and I saw we're not deleting it.I also tried to run other PUT method calls like create bucket with proxy, no issues there, just when trying to upload uploads into the bucket.
Note
When trying to upload a non-empty file with the same method above (aws cli), facing different issue where it can't connect to the proxy:
The text was updated successfully, but these errors were encountered: