➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2013-02-20 23:20 by Wilson.Harron, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| proxytest.py | Wilson.Harron, 2013-02-20 23:20 | a quick example of the error seen - the error occurs on line 58 | ||
| Messages (2) | |||
|---|---|---|---|
| msg182567 - (view) | Author: Wilson Harron (Wilson.Harron) | Date: 2013-02-20 23:20 | |
If a manager is running listening to all ports ('0.0.0.0') and the manager has a proxy that returns another proxy the client will not be able to create the resulting proxy.
This is because the server (manager) returns '0.0.0.0' in the token returned, and the therefore the client cannot connect to the proxy.
|
|||
| msg192191 - (view) | Author: Roundup Robot (python-dev)  |
Date: 2013-07-02 12:41 | |
New changeset 20b59fec1123 by Richard Oudkerk in branch '2.7': Issue #17261: Ensure multiprocessing's proxies use proper address. http://hg.python.org/cpython/rev/20b59fec1123 New changeset be4b9e677187 by Richard Oudkerk in branch '3.3': Issue #17261: Ensure multiprocessing's proxies use proper address. http://hg.python.org/cpython/rev/be4b9e677187 New changeset 7387b884f833 by Richard Oudkerk in branch 'default': Issue #17261: Ensure multiprocessing's proxies use proper address. http://hg.python.org/cpython/rev/7387b884f833 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:42 | admin | set | github: 61463 |
| 2013-07-02 12:41:56 | sbt | set | status: open -> closed stage: resolved resolution: fixed versions: + Python 3.3, Python 3.4 |
| 2013-07-02 12:41:04 | python-dev | set | nosy:
+ python-dev messages: + msg192191 |
| 2013-02-21 10:34:54 | sbt | set | nosy:
+ sbt |
| 2013-02-20 23:20:42 | Wilson.Harron | create | |