bugfix: user-agent python-requests

[mtricolici98]

Replaced user agent to avoid bot protection on private repositories.

For lock and install commands, the requests library was used, resulting in HTTP requests with 'python-requests' User-agent being sent.

It is possible that HTTP Servers (such as OPNSens in my case) have 'bot protection' to automatically block "bot-like" user agents.

This quick fix comes as a counter measure for the following problem.

Pull Request Check List

Resolves: No tracked issue

• No code tests updated
• No documentation updates necessary

[dimbleby]

this all seems a bit silly to me: a repository that doesn't allow downloads from the requests user agent is broken and should be fixed (or reconfigured)

however it also seems harmless enough I suppose

[dimbleby]

or {} isn't doing anything useful

cf

poetry/src/poetry/publishing/uploader.py

Line 82 in 02448cf

session.headers["User-Agent"] = self.user_agent

, which does this on the session - it would be consistent here to do the work in create_session().

[mtricolici98]

I think or {} covers the potential of there being a headers key in the dict with a None value.

I will apply the UA to the session itself. Thank you for the suggestion.

[mtricolici98]

this all seems a bit silly to me: a repository that doesn't allow downloads from the requests user agent is broken and should be fixed (or reconfigured)

however it also seems harmless enough I suppose

I do agree, it took me a while to figure out that the 403 I was receiving wasn't from bad credentials or authorization but from the user agent. It seems like our repository is proxied through a nginx configuration that blocks some "bot like" user agents, as to "protect" from vulnerability scans or other bot activity. A quick curl with 2 different user agent headers cleared that one for me. However the dev-ops team on my project is reluctant to disable the bot protection.
Thus I created a quite silly plugin to inject the ua headers, and thought it might be fine to also solve this at the source, especially since poetry provides his own user agent during the publishing step, it makes sense that for consistency it will also use the poetry UA.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.