-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Content-Type is always set #457
Comments
When you send request you know content type, isn't it? As an option we may add What's your use case? Why S3's signed URLs are not aware about content type? |
As far as I remember issues with s3 is following: s3 api requires special signature to be added, when you preparing request. So you take body and headers then calculate signature, but |
Well, |
@chrisseto I tested my implementation with almost all tests (except pagination) of botocore library and it works as expected. |
See also #379 |
@chrisseto we don't autoset
|
Using In [5]: aiohttp.__version__
Out[5]: '0.14.1'
In [6]: asyncio.get_event_loop().run_until_complete(aiohttp.request('GET', 'http://localhost:1234')) ~❯❯❯ nc -l 1234
GET / HTTP/1.1
ACCEPT: */*
ACCEPT-ENCODING: gzip, deflate
HOST: localhost:1234
CONTENT-LENGTH: 0
CONNECTION: keep-alive
USER-AGENT: Python/3.4 aiohttp/0.14.1 |
Ahh, got it. Sorry. |
for |
I think we can close this one |
As of 089e829 the Content-Type header is alway set if not otherwise set by the user.
This behavior is often undesirable and should be opt-in or at least provide an option to opt-out.
In the case of using Amazon S3's signed URLs, extra steps must be taken to have this header included.
The text was updated successfully, but these errors were encountered: