-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
xmlrpc.client ignores query in URI ("?action=xmlrpc2") since python-3.9 #87599
Comments
xmlrpc.client proxy behaviour changed and broke tools depending on URI containing query part. Last working version: https://github.com/python/cpython/blob/3.8/Lib/xmlrpc/client.py#L1417 Changed behaviour here: https://github.com/python/cpython/blob/3.9/Lib/xmlrpc/client.py#L1424 Is this change intended? If so, what is recommended solution for xmlrpc client communicating with URI: http://example.com/path?var=foo ? |
Reproducer:
Old behavior: New behaviour: |
Can confirm. This changed in bpo-38038 and the fix isn't too difficult. Adding 3.10 in case it's decided that this shouldn't be patched onto 3.9. |
Thank you for your reports OndrejPtak and frathgeber. Indeed, the behavior change was unintended. PR 25057 tries to to restore the old behavior. Query and fragment are now preserved in the server URL. But there are still minor differences. Empty query and fragment are stripped from the URL, so "http://example.org/RPC2?", "http://example.org/RPC2#" and "http://example.org/RPC2" refer to the same connection point. I am not sure that it is important. It would be not easy to preserve the old behavior in these corner cases. |
Thanks Serhiy for the very quick fix! I believe handling these corner cases is not worth the effort and I really hope no one relies on these being differentiated. This change will go into a future 3.9 release? |
It seems like the issue is now fixed. Thanks Serhiy for the fix and thanks OndrejPtak for the report!
Yes, sure. Python 3.9 Release Schedule: Next expected release: Python 3.9.3: Monday, 2021-05-03. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: