[issue25080] The example-code for making XML-RPC requests through proxy, fail!

Changes by Raymond Hettinger <raymond.hettin...@gmail.com>: -- title: The example-code for making XLM-RPC requests through proxy, fail! -> The example-code for making XML-RPC requests through proxy, fail! ___ Python tracker <rep...@bug

[issue25080] The example-code for making XLM-RPC requests through proxy, fail!

Changes by Berker Peksag : -- components: -Demos and Tools stage: -> needs patch type: -> behavior versions: +Python 3.5, Python 3.6 ___ Python tracker

[issue25080] The example-code for making XLM-RPC requests through proxy, fail!

New submission from Kostis ankostis: The example code provided at the bottom of the reference-page: https://docs.python.org/2/library/xmlrpclib.html#example-of-client-usage for making XML-RPC requests through a proxy by defining a custom transport fails (at least) in python-3.4! Obviously

[issue25068] The proxy key's string should ignore case.

Chris Angelico added the comment: This sounds like a feature enhancement, which means it (almost certainly) won't be applied to Python 2.7. Does the same question come up in Python 3? Also (FWIW) if you can confidently assume that all the keys are strings. then type.lower() is better than

[issue25068] The proxy key's string should ignore case.

Martin Panter added the comment: On the other hand, a documentation update saying it has to be lower case would be fine for Python 2.7 and 3.4+, if you wanted to go that way. -- ___ Python tracker

[issue25068] The proxy key's string should ignore case.

Martin Panter added the comment: Looking at the code, I think Python 3 is in the same boat. Most things in Python are case-sensitive, but I think it is reasonable to make an exception here, since the protocol schemes in general are insensitive. E.g.

[issue25068] The proxy key's string should ignore case.

New submission from Chuang Cao: When use a urllib2.ProxyHandler to set a proxy, if the proxies's key is an upper string, like "HTTP", "HTTPS". The proxy url can't be used, because they can't find the _open function. Two way can sovle the issue. 1. Specify it in document

[issue7291] urllib2 cannot handle https with proxy requiring auth

not distinguish the 407 Proxy Authentication Required error of the initial proxy CONNECT request from any potential 407 response from a tunnelled connection. Perhaps a special case could be made; I think there are already lots of special cases. But the maze of urlopen() handlers is already too

[issue1424152] urllib/urllib2: HTTPS over (Squid) Proxy fails

Martin Panter added the comment: In the meantime, Issue 24599 has been opened about URLopener(), which I understand is related to the Python 2 “urllib” half of this bug. Since this issue has been closed, perhaps it is best to continue discussion of issue1424152-py27-urllib.diff there instead.

[issue16095] urllib2 failing with squid proxy and digest authentication

Martin Panter added the comment: There are two problems with the test case, and one bug in Python: 1. HTTPPasswordMgr doesn’t handle realm=None; it has to be a string. You can use HTTPPasswordMgrWithDefaultRealm though. 2. The password managers won’t match a proxy with a non-standard port

[issue16095] urllib2 failing with squid proxy and digest authentication

Martin Panter added the comment: I should point out my patch also adds add_password() methods for the authentication handlers to the documentation. These were only documented by example, but everyone seems to prefer using them rather than the equivalent password manager method. --

[issue24393] Test urllib2_localnet fails depending on host proxy configuration

Changes by Ned Deily n...@acm.org: -- nosy: +orsenthil stage: - patch review versions: +Python 3.6 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24393 ___

[issue24393] Test urllib2_localnet fails depending on host proxy configuration

Étienne Buira added the comment: Patch was for 2.7 Hunks about no_proxy are also relevant for other branches. -- versions: +Python 3.2, Python 3.3, Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24393

[issue24333] urllib2 HTTPS connection over a digest auth enabled proxy gives 407

New submission from Chi Hsuan Yen: This is originally my question at stackoverflow.com. (http://stackoverflow.com/q/30511341/3786245) I think it's a bug, so I posted it here. I'm trying to fetch HTTPS pages through a proxy with digest authentication. Here are my codes: import urllib.request

[issue24333] urllib2 HTTPS connection over a digest auth enabled proxy gives 407

. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed -http_access allow localnet -http_access allow localhost +# http_access allow localnet +# http_access allow localhost +auth_param digest realm Proxy digest auth test +auth_param digest

[issue24333] urllib2 HTTPS connection over a digest auth enabled proxy gives 407

with proxy requiring auth ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24333 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue7291] urllib2 cannot handle https with proxy requiring auth

Martin Panter added the comment: I believe this also affects Python 3; see Issue 24333. I think making the CONNECT response object available to the caller is the right general approach. But I really dislike raising an exception that holds a socket connection to be closed. (I know this is

[issue15928] Open url with proxy causes TypeError

Changes by Martin Panter vadmium...@gmail.com: -- resolution: not a bug - duplicate superseder: - Missing size argument in readline() method for httplib's class LineAndFileWrapper ___ Python tracker rep...@bugs.python.org

[issue24311] urllib2.urlopen() through proxy fails when HTTPS URL contains port number

Serhiy Storchaka added the comment: Thank you for your report Atzm. -- assignee: - serhiy.storchaka resolution: - duplicate stage: - resolved status: open - closed superseder: - Use of set_tunnel with default port results in incorrect post value in host header type: - behavior

[issue24311] urllib2.urlopen() through proxy fails when HTTPS URL contains port number

New submission from Atzm WATANABE: urllib2.urlopen() through proxy causes ssl.CertificateError when HTTPS URL contains port number. Sample code: $ https_proxy='http://proxy.example.com:8080/' python -c 'import urllib2; urllib2.urlopen(https://www.python.org:443/;)' Traceback (most recent

[issue24311] urllib2.urlopen() through proxy fails when HTTPS URL contains port number

Changes by Ned Deily n...@acm.org: -- nosy: +serhiy.storchaka ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24311 ___ ___ Python-bugs-list mailing

SOAPpy proxy through NTLM

, password, instance = 'domain\\user', 'abc123', 'demo' proxy, namespace = 'http://username:password@networkchange/NetworkChangeAPI.asmx'+instance+'/incident.do?SOAP', 'http://networkchange/webservices/' server = SOAPProxy(proxy,namespace) server.config.debug = 1 response = server.GetBlankRfc

[issue23502] pprint: added support for mapping proxy

Roundup Robot added the comment: New changeset 646a7e1da7f0 by Serhiy Storchaka in branch 'default': Issue #23502: The pprint module now supports mapping proxies. https://hg.python.org/cpython/rev/646a7e1da7f0 -- nosy: +python-dev ___ Python tracker

[issue23502] pprint: added support for mapping proxy

Changes by Serhiy Storchaka storch...@gmail.com: -- assignee: - serhiy.storchaka resolution: - fixed stage: patch review - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23502

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Davin Potts added the comment: Per Richard's post from 1 year ago where he offers both explanation and an example, ultimately concluding that things are working as intended, and because there have been no objections or requests for clarification in the past year, closing this and marking it

[issue19547] HTTPS proxy support missing without warning

Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19547 ___ ___ Python-bugs-list

[issue19547] HTTPS proxy support missing without warning

Changes by Demian Brecht demianbre...@gmail.com: -- nosy: +demian.brecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19547 ___ ___

[issue19547] HTTPS proxy support missing without warning

Demian Brecht added the comment: It very well could be. I'd like to be able to repro it first though. I'll try to get some time to look into it, but if someone else can confirm this behavior and attach a test case, that would be great. -- stage: - test needed

[issue19547] HTTPS proxy support missing without warning

Mark Lawrence added the comment: Should this be classifed as a security issue? -- nosy: +BreamoreBoy versions: -Python 2.6, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19547

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Changes by Demian Brecht demianbre...@gmail.com: -- nosy: +demian.brecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23328 ___ ___

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Martin Panter added the comment: This should demonstrate that Curl does parse literal slashes in the username and password fields: $ http_proxy=http://user/name:pass/word@localhost:22 curl -v http://example.net/ * Trying ::1... * Connected to localhost (::1) port 22 (#0) * Proxy auth using

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Panagiotis Issaris added the comment: RFC3986 seems to state that a '/' character should be encoded: ... reserved= gen-delims / sub-delims gen-delims = : / / / ? / # / [ / ] / @ sub-delims = ! / $ / / ' / ( / ) / * / + / , / ; / = ... The user information, if present,

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Andy Reitz added the comment: Sure, but the question is who should do the encoding -- the user, or python? I think it would be better for python to read the password from the environment variable, and encode it before using it. I think this is what users expect. --

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Martin Panter added the comment: To comply with the RFC on URLs, whoever is setting the environment variable _should_ do the encoding, and then Python will _decode_ it. But I suspect this case is more about how Python should handle an environment variable that hasn’t been encoded correctly.

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Senthil Kumaran added the comment: In the initial report, I thought, it was mentioned that curl reads the same http_proxy variable properly. It will be good to have a correct curl test case to ascertain that. But, at all the places, where @ character is allowed in urls (netrc, git configs,

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Martin Panter added the comment: The relevant code looks like it is _parse_proxy() at Lib/urllib/request.py:693. It has custom code to search for a slash (/), so it wouldn’t be hard to make it search after the last at (@) symbol. (I previously assumed it would use urlsplit() or similar, which

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Martin Panter added the comment: Related: Issue 18140. The slash character is meant to be a reserved character in URLs, so why hasn’t it been encoded? Where does the environment variable come from? -- nosy: +vadmium ___ Python tracker

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Andy Reitz added the comment: The proxy credentials are supplied by our sysadmin. My understanding is that the http_proxy env variable doesn't require URI encoding. In addition, the same credentials work fine with curl. -- ___ Python tracker rep

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Senthil Kumaran added the comment: Yup, can confirm that this is problem. As Andy recognized, there is parsing error that fails on '/' character in the password. The environ based proxies are used by urllib rather than urllib2. (The test case if relies on environ proxy, should use

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

://www.python.org') data = f.read() print data I expect this error message (because my sample proxy is totally bogus): [areitz@SOMEHOST ~]$ python2.7 test.py Traceback (most recent call last): File test.py, line 3, in module f = urllib.urlopen('http://www.python.org') File /usr/lib64

[issue23328] urllib2 fails for proxy credentials that contain a '/' character

Andy Reitz added the comment: Sorry, went a bit too quickly -- here is the sample code that I meant to use: import os, urllib2 os.environ['http_proxy'] = http://someuser:a/b@10.11.12.13:1234; f = urllib2.urlopen('http://www.python.org') data = f.read() print data And the stack trace

Re: Suds Python 2.4.3 Proxy

On Sun, Nov 30, 2014 at 2:01 AM, Jerry Rocteur jerry.roct...@gmail.com wrote: This works GREAT on 2.7 but when I run it on 2.4 I get: File /usr/lib64/python2.4/urllib2.py, line 580, in proxy_open if '@' in host: TypeError: iterable argument required It might be worth looking at some

Re: Suds Python 2.4.3 Proxy

On 30/11/2014 09:10, Chris Angelico wrote: On Sun, Nov 30, 2014 at 2:01 AM, Jerry Rocteur jerry.roct...@gmail.com wrote: This works GREAT on 2.7 but when I run it on 2.4 I get: File /usr/lib64/python2.4/urllib2.py, line 580, in proxy_open if '@' in host: TypeError: iterable argument

Re: Suds Python 2.4.3 Proxy

In article captjjmowa3byvgd4cg9yh2cuucqaj+cpjsugxwnnvgt1tb8...@mail.gmail.com, Chris Angelico ros...@gmail.com wrote: It might be worth looking at some actual 2.4 documentation. Unfortunately that doesn't seem to be hosted on python.org any more (though I might be wrong), https://python.org/

Re: Suds Python 2.4.3 Proxy

On Mon, Dec 1, 2014 at 8:14 AM, Ned Deily n...@acm.org wrote: In article captjjmowa3byvgd4cg9yh2cuucqaj+cpjsugxwnnvgt1tb8...@mail.gmail.com, Chris Angelico ros...@gmail.com wrote: It might be worth looking at some actual 2.4 documentation. Unfortunately that doesn't seem to be hosted on

Suds Python 2.4.3 Proxy

there but now I have to deploy the script on some Redhat workstations running python 2.4.3 (which I am not allowed to upgrade) When I create my client in my script I do it like this: url = 'https://system.globalsign.com/cr/ws/GasOrderService?wsdl' proxy = {'https': proxylog + : + proxypass

[issue7291] urllib2 cannot handle https with proxy requiring auth

Mark Lawrence added the comment: Is there any work still needed here? Surely the 2.6.x patches can't be applied unless there are security issues? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7291

[issue17518] urllib2 cannnot handle https and BasicAuth via Proxy.

Mark Lawrence added the comment: Slipped under the radar? Note the patch suggested in msg184958. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17518 ___

[issue9643] urllib2 - Basic, Digest Proxy Auth Handlers failure will give 401 code instead of 407

Mark Lawrence added the comment: Slipped under the radar? -- components: +Library (Lib) nosy: +BreamoreBoy type: - behavior versions: +Python 3.4, Python 3.5 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9643

Re: Google Appengine Proxy Post method error

alextr...@googlemail.com wrote: So I got the Labnol Google Appengine proxy but it can't handle the Post method aka error 405. I need help adding this method to the script: mirror.py = http://pastebin.com/2zRsdi3U transform_content.py = http://pastebin.com/Fw7FCncA main.html = http

Google Appengine Proxy Post method error

So I got the Labnol Google Appengine proxy but it can't handle the Post method aka error 405. I need help adding this method to the script: mirror.py = http://pastebin.com/2zRsdi3U transform_content.py = http://pastebin.com/Fw7FCncA main.html = http://pastebin.com/HTBH3y5T All other files

[issue16095] urllib2 failing with squid proxy and digest authentication

the username and password for the proxy, the function find_user_password(realm, req.full_url) gets executed. An example, if my proxy has the address abc.com:8080 and my request is for xyz.com, the function tries to find a password for the xyz.com url, instead of the abc.com:8080 url. So it can't

Re: Define proxy in windows 7

On 02/09/2014 04:02, Chris Angelico wrote: These tips may help. (Though on Windows, where port 80 requires no special privileges, it's more likely for a proxy to use that than it is under Unix. So it's entirely possible it is actually on 80.) But what I'm seeing is a problem with environment

Define proxy in windows 7

Hi, I am wondering how to define proxy setting in env variable on windows 7, I want this so i can use pip to pull packages for me, the same setting though working earlier on windows xp. http_proxy = proxy name:80 now this same setting doesn't work, i tried doing in the cmd.exe prompt. set

Re: Define proxy in windows 7

On 02Sep2014 06:25, Om Prakash torque.in...@gmail.com wrote: I am wondering how to define proxy setting in env variable on windows 7, I want this so i can use pip to pull packages for me, the same setting though working earlier on windows xp. http_proxy = proxy name:80 now this same

Re: Define proxy in windows 7

On Tue, Sep 2, 2014 at 12:06 PM, Cameron Simpson c...@zip.com.au wrote: I am not a Windows user, but on UNIX systems the format of http_proxy and https_proxy is: http://proxyname:3128/ being the proxy hostname and port number respectively. You're saying: proxyname:8080 instead. (Note

[issue22041] http POST request with python 3.3 through web proxy

that this problem is related to proxy configuration. However, I'll take in count which version of Python to use if I have to do a similar job. Regards, Alejandro -- resolution: - not a bug ___ Python tracker rep...@bugs.python.org http

[issue22041] http POST request with python 3.3 through web proxy

Demian Brecht added the comment: No problem, happy you were able to get things sorted. Feel free to close this issue as I've opened #22095 to address the host port header issue. -- ___ Python tracker rep...@bugs.python.org

[issue22041] http POST request with python 3.3 through web proxy

Changes by Ned Deily n...@acm.org: -- stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22041 ___ ___

[issue22041] http POST request with python 3.3 through web proxy

Alejandro MJ added the comment: Thanks a lot for your help! I've tested it in Linux, Python version 3.3.5 and the message obtained is this: [404 Not Found]. The script is this one (changing of course the ip_address and the proxy_url values): import http.client, urllib.parse data =

[issue22041] http POST request with python 3.3 through web proxy

Alejandro MJ added the comment: I've wrote these sentences on my SUSE, python is installed on path: /usr/local/pr/python computer002:/usr/local/pr/python # patch -p1 --dry-run issue22041_1.patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text

[issue22041] http POST request with python 3.3 through web proxy

Demian Brecht added the comment: To add a little more detail, from what I gather, CONNECT support may be unsupported or limited (i.e. only allowing SSL connections) on various proxy servers. If the code snippet in my previous post solves your issue, then I would assume that to be the case

[issue22041] http POST request with python 3.3 through web proxy

. At this point, I'm relatively confident that the issue is due to the proxy server in use. Using your latest code but a local squid proxy, I'm able to get 200 responses with the latest releases of 3.3 and 3.4 as well as against dev. Do you absolutely need to tunnel? The most common use case

[issue22041] http POST request with python 3.3 through web proxy

Demian Brecht added the comment: I've attached a patch that solves the issue I encountered. It would be great if you could confirm whether or not it also resolves the issue as reported. -- keywords: +patch Added file: http://bugs.python.org/file36066/issue22041.patch

[issue22041] http POST request with python 3.3 through web proxy

Demian Brecht added the comment: Attached a new patch with with a simple test. -- Added file: http://bugs.python.org/file36079/issue22041_1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22041

[issue22041] http POST request with python 3.3 through web proxy

Changes by Alejandro Mj witchar...@gmail.com: -- nosy: -AlexMJ ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22041 ___ ___ Python-bugs-list

[issue22041] http POST request with python 3.3 through web proxy

Changes by Demian Brecht demianbre...@gmail.com: -- nosy: +demian.brecht ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22041 ___ ___

[issue22041] http POST request with python 3.3 through web proxy

(resp.code, 200) # FAILS con.close() if __name__ == '__main__': unittest.main() As you can see with the test above, if I use the full URI, the request succeeds, but the relative path (as in your example) fails. My assumption is that these issues may be related to proxy server

[issue22041] http POST request with python 3.3 through web proxy

Demian Brecht added the comment: Ignore my previous note. Digging into this a little more, I think I've possibly found the underlying issue: If the port is not specified in set_tunnel (as in your example), the buffer sent over the wire looks like send: b'POST [PATH] HTTP/1.1\r\nHost:

[issue22041] http POST request with python 3.3 through web proxy

() It works perfectly when I test it without a proxy, but when I try with proxy connection, I receive this error: conn.request(POST, /es/spain/people.aspx, data, headers) Traceback (most recent call last): File stdin, line 1, in module File C:\Python34\lib\http\client.py, line 1090, in request

[issue12480] urllib2 doesn't use proxy (fieddler2), configed the proxy with ProxyHandler

Mark Lawrence added the comment: @Senthil what if anything can we do with this issue? -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12480 ___

[issue16095] urllib2 failing with squid proxy and digest authentication

Mark Lawrence added the comment: Can we have an update on this please. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16095

[issue16095] urllib2 failing with squid proxy and digest authentication

Pietro Battiston added the comment: The bug is still present in 2.7.7 and 3.4.1. By the way, under python 3 the workaround takes the form class MyHTTPPasswordMgr(urllib.request.HTTPPasswordMgr): def find_user_password(self, realm, authuri): return a, b Finally, notice the wrong

[issue11511] Proposal for exposing proxy bypass settings in ProxyHandler

Mark Lawrence added the comment: Can we have a patch review on this please. -- nosy: +BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11511 ___

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Richard Oudkerk added the comment: For reasons we all know unpickling unauthenticated data received over TCP is very risky. Sending an unencrypted authentication key (as part of a pickle) over TCP would make the authentication useless. When a proxy is pickled the authkey is deliberately

[issue20854] multiprocessing.managers.Server: problem with returning proxy of registered object

seems to me somewhat counterintuitive. Another issue that arises in my case is: when I try to pass a proxy of MyClass to a subprocess it looses its' _manager during pickling and thus the ability to create proxies for children returned by get_child. This is solved by reimplementing

[issue20854] multiprocessing.managers.Server: problem with returning proxy of registered object

Richard Oudkerk added the comment: I am not sure method_to_typeid and create_method were really intended to be public -- they are only used by Pool proxies. You can maybe work around the problem by registering a second typeid without specifying callable. That can be used in method_to_typeid:

[issue20854] multiprocessing.managers.Server: problem with returning proxy of registered object

This means that if ANY method registered with a Manager should return a proxy for a registered typeid, for which a callable is provided, it will fail, unless the callable is capable to handle such unexpected arguments. -- components: Library (Lib) messages: 212763 nosy: allista priority

[issue20854] multiprocessing.managers.Server: problem with returning proxy of registered object

Changes by Ned Deily n...@acm.org: -- nosy: +sbt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20854 ___ ___ Python-bugs-list mailing list

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Changes by Richard Oudkerk shibt...@gmail.com: -- assignee: - sbt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7503 ___ ___ Python-bugs-list

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Paul Tunison added the comment: I can confirm that this is still an issue with python 2.7.5. My method of resolving this locally is similar to xhantu's. I created a sub-class of BaseProxy, overriding the __reduce__ method and injecting the authkey into the appropriate spot in the super

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Paul Tunison added the comment: I can confirm that this is still an issue with python 2.7.5. My method of resolving this locally is similar to xhantu's. I created a sub-class of BaseProxy, overriding the __reduce__ method and injecting the authkey into the appropriate spot in the super

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Paul Tunison added the comment: I can confirm that this is still an issue with python 2.7.5. My method of resolving this locally is similar to xhantu's. I created a sub-class of BaseProxy, overriding the __reduce__ method and injecting the authkey into the appropriate spot in the super

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Dhanannjay Deo added the comment: Confirmed for python 2.7.3 on ubuntu 12.04 lts. Why this issue is still open after 4 years ? -- nosy: +Dhanannjay.Deo versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7503

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Ned Deily added the comment: [Note, due to a bug tracker error now fixed, s couple of comments made to this issue earlier today were dropped. I'm manually adding them here on behalf of the original submitters.] At Wed Feb 26 17:05:01 CET 2014, Paul Tunison added the comment: I can confirm

[issue7503] multiprocessing AuthenticationError digest sent was rejected when pickling proxy

Ned Deily added the comment: At Wed Feb 26 17:09:49 CET 2014, Dhanannjay Deo added the comment: Confirmed for python 2.7.3 on ubuntu 12.04 lts. Why this issue is still open after 4 years ? -- nosy: +Dhanannjay.Deo versions: -Python 2.6 ___ Python

[issue7291] urllib2 cannot handle https with proxy requiring auth

Vackar Afzal added the comment: I've found that for the Python2.6.x patch to play nicely with the popular rquests library, I've had to set some defaults on the modified __init__ function so that it reads as follows: def __init__(self, *args, **kwargs): _orig_init(self, *args,

[issue7291] urllib2 cannot handle https with proxy requiring auth

Vackar Afzal added the comment: Also needed to make another minor update to the monkey patch. Have uploaded the new files as new_http_proxy_patch.py for use with python 2.6.x -- Added file: http://bugs.python.org/file34174/new_http_proxy_patch.py ___

[issue8238] Proxy handling

Changes by Mark Lawrence breamore...@yahoo.co.uk: -- nosy: -BreamoreBoy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8238 ___ ___

Re: Want guidance to set proxy please help

On Sun, 15 Dec 2013 20:29:55 -0800, Jai wrote: so , i need some step to set proxy so that my ip is not blocked by them This sounds like you're attempting to access a site other than for legitimate purposes. You probably want some 1337 script kiddies forum, not a serious programming newsgroup

Want guidance to set proxy please help

hey i am working on parsing like project . so , i need some step to set proxy so that my ip is not blocked by them += i am using this method proxy_support = urllib2.ProxyHandler({http:http://61.147.82.87:8000}) opener = urllib2.build_opener(proxy_support

want to run proxy in python

hey , will u guide me how to run proxies from python i have tested lots of code but my ip show always constant on when i see it online plz help . -- https://mail.python.org/mailman/listinfo/python-list

Re: want to run proxy in python

On Fri, 13 Dec 2013 03:39:44 -0800, Jai wrote: hey , will u guide me how to run proxies from python http://lmgtfy.com/?q=ip+address+spoofing -- Denis McMahon, denismfmcma...@gmail.com -- https://mail.python.org/mailman/listinfo/python-list

please guide to make proxy type function in python

please guide to make proxy type function in python -- https://mail.python.org/mailman/listinfo/python-list

Re: please guide to make proxy type function in python

On 11/12/2013 12:28, Jai wrote: please guide to make proxy type function in python Write some code after looking at the documentation http://docs.python.org/3/. -- My fellow Pythonistas, ask not what our language can do for you, ask what you can do for our language. Mark Lawrence

[issue19864] multiprocessing Proxy docs need locking semantics explained

Richard Oudkerk added the comment: From what I remember a proxy method will be thread/process-safe if the referent's corresponding method is thread safe. It should certainly be documented that the exposed methods of a proxied object should be thread-safe

Re: reporting proxy porting problem

On 28/11/2013 22:01, Terry Reedy wrote: .. All the transition guides I have seen recommend first updating 2.x code (and its tests) to work in 2.x with *all* classes being new-style classes. I presume one of the code checker programs will check this for you. To some extent, the

[issue19864] multiprocessing Proxy docs need locking semantics explained

New submission from Max Polk: In the docs (both Python 2 and 3) for the multiprocessing module, the Proxy section needs to be explicit about the fact that is does NOT create locks around access to shared objects. Why? Because on the same page, we read about

[issue19864] multiprocessing Proxy docs need locking semantics explained

Changes by Ned Deily n...@acm.org: -- nosy: +sbt versions: +Python 2.7, Python 3.3, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19864 ___

reporting proxy porting problem

I am in the process of porting reportlab to python3.3, one of the contributions is a module that implements a reporting proxy with a canvas that records all access calls and attribute settings etc etc. This fails under python3 because of differences between old and new style classes. I find

<    1   2   3   4   5   6   7   8   9   10   >