Get Request is used when Post Request is Used.

[DuckMasterAl]

🐞 Describe the bug

Aiohttp uses the get request instead of the post request.

💡 To Reproduce

1. This was run on a discord.py bot, but it may work in other environments.
2. Run the following code:

import aiohttp
async with aiohttp.ClientSession() as session:
  async with session.post(f'http://api.trello.com/1/cards') as r:
    return await r.text()

3. Notice you get a Cannot GET /1/cards error. This doesn't happen in other instances like curl where you get an invalid key error (see below)

💡 Expected behavior

The request was done via a push request.

📋 Logs/tracebacks

None

📋 Your version of the Python

$ python3 --version
Python 3.8.0

📋 Your version of the aiohttp/yarl/multidict distributions

$ python3 -m pip show aiohttp
Name: aiohttp
Version: 3.6.2
Summary: Async http client/server framework (asyncio)
Home-page: https://github.com/aio-libs/aiohttp
Author: Nikolay Kim
Author-email: [email protected]
License: Apache 2
Location: /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages
Requires: yarl, async-timeout, attrs, multidict, chardet
Required-by: discord.py, dblpy

$ python3 -m pip show multidict
Name: multidict
Version: 4.5.2
Summary: multidict implementation
Home-page: https://github.com/aio-libs/multidict
Author: Andrew Svetlov
Author-email: [email protected]
License: Apache 2
Location: /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages
Requires: 
Required-by: yarl, aiohttp

$ python3 -m pip show yarl
Name: yarl
Version: 1.3.0
Summary: Yet another URL library
Home-page: https://github.com/aio-libs/yarl/
Author: Andrew Svetlov
Author-email: [email protected]
License: Apache 2
Location: /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/site-packages
Requires: multidict, idna
Required-by: aiohttp

📋 Additional context

Using it in a discord bot vs using reqbin

The bot is able to properly post to other sites, but not api.trello.com

[Maillol]

POST to 'http://api.trello.com/1/cards' returns a 301:

$ curl -D - -X POST http://api.trello.com/1/cards
HTTP/1.1 301 Moved Permanently
location: https://api.trello.com/1/cards
date: Wed, 30 Sep 2020 19:53:56 GMT
server: envoy
content-length: 0

This behaviour seems expected.

it is a duplicate: #3082

According to rfc2616:

10.3.2 301 Moved Permanently

 If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. 

      Note: When automatically redirecting a POST request after
      receiving a 301 status code, some existing HTTP/1.0 user agents
      will erroneously change it into a GET request.

10.3.3 302 Found

    Note: RFC 1945 and RFC 2068 specify that the client is not allowed
    to change the method on the redirected request.

[DuckMasterAl]

Oh ok, thanks for the help!