30X upload redirect bug, fails but reports success #7159
Description
- Poetry (version 1.2.2):
- 3.11:
- Debian GNU/Linux 10 (buster), 4.19.0-22-amd64:
- **pyproject.toml **:
- I am on the latest stable Poetry version, installed using a recommended method.
- I have searched the issues of this repo and believe that this is not a duplicate.
- I have consulted the FAQ and blog for any relevant entries or release notes.
- If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption) and have included the output below.
Issue
When publishing with poetry and the response is in the 300 range, (other then 301) the upload reports success but upload does not succeed. This also happened with 308.
$ poetry publish --repository foo -vvv
Adding repository foo (http://x.x.x.173:8090/redirect)
[keyring.backend] Loading KWallet
[keyring.backend] Loading SecretService
[keyring.backend] Loading Windows
[keyring.backend] Loading chainer
[keyring.backend] Loading libsecret
[keyring.backend] Loading macOS
No suitable keyring backend found
No suitable keyring backends were found
Keyring is not available, credentials will be stored and retrieved from configuration files as plaintext.
Found authentication information for foo.
Publishing poetry-demo (0.1.0) to foo
- Uploading poetry_demo-0.1.0-py3-none-any.whl 0%[urllib3.connectionpool] Starting new HTTP connection (1): x.x.x.173:8090
- Uploading poetry_demo-0.1.0-py3-none-any.whl 100%[urllib3.connectionpool] http://x.x.x.173:8090 "POST /redirect HTTP/1.1" 302 0
- Uploading poetry_demo-0.1.0.tar.gz 100%[urllib3.connectionpool] http://x.x.x.173:8090 "POST /redirect HTTP/1.1" 302 0
I have a PR written to fix this, will submit in conjunction with this.
PR: #7160