s3proxy icon indicating copy to clipboard operation
s3proxy copied to clipboard

Error: Unknown header x-amz-te with URI (Camel aws2-s3)

Open radekcz opened this issue 2 years ago • 5 comments

When I try to use s3proxy for testing aws2-s3 component from Apache Camel, I keep getting Error:

[S3Proxy-Jetty-46] ERROR org.gaul.s3proxy.S3ProxyHandler - Unknown header x-amz-te with URI

I know this issue can be solved by the configuration of s3-client but when I use Camel aws2-s3 component, I'm not able to change this setting. So is it possible to implement/ignore this attribute on s3proxy side? Thanks a lot.

Maybe related to: https://github.com/aws/aws-sdk-java-v2/issues/1974

radekcz avatar Apr 11 '22 15:04 radekcz

This seems like an unfortunate default behavior from your client. I believe that this is related to additional checksum algorithms. Ideally S3Proxy would add full support for this, at least enforcing the checksum during upload. But ignoring the header is probably a sufficient workaround.

gaul avatar Apr 16 '22 07:04 gaul

Same here:

[s3proxy] E 11-08 19:22:29.118 S3Proxy-Jetty-12 o.gaul.s3proxy.S3ProxyHandler:640 |::] Unknown header x-amz-user-agent with URI 

unfortunate default behavior from your client:

Unfortunatelly, that would be the official from AWS:

X-Amz-User-Agent: aws-sdk-js/2.1161.0 promise

juangburgos avatar Nov 08 '23 19:11 juangburgos

Having the same issue as juangburgos

Blackfaded avatar Nov 28 '23 15:11 Blackfaded

Having the same issue as juangburgos

s3proxy.ignore-unknown-headers=true helped

juangburgos avatar Nov 28 '23 15:11 juangburgos

Having the same issue as juangburgos

s3proxy.ignore-unknown-headers=true helped

Thanks a lot! Made the config via docker-compose with

- S3PROXY_IGNORE_UNKNOWN_HEADERS=true

That also worked

Blackfaded avatar Nov 28 '23 15:11 Blackfaded