You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if no_proxy is written with blank spaces between comma, it will not be correctly handled.
example : no_proxy='example1.com, example2.com'
In addition, by looking at the code I am not sure the following will be correctly handled either: no_proxy='example1.com,*,example2.com'
OK there is no sense of doing that but it has no reason not to work !?
support of IP range (e.g 10.0.0.0/24) might be also good !
maybe the better would the to
-split the content the of no_proxy variable
-iterate over each splitted string
----remove blankspace at the beginning and the end
----check for forbbiden character (report as warning and ignore ?)
----recognize IP address and also IP address range
----append one (or many in case of IP range) to the bypass_hosts attribute of ProxyInfo class
-replace the by_pass_host method by using a unix-style regex (maybe glob library ?)
The text was updated successfully, but these errors were encountered:
Hi,
if no_proxy is written with blank spaces between comma, it will not be correctly handled.
example :
no_proxy='example1.com, example2.com'
In addition, by looking at the code I am not sure the following will be correctly handled either:
no_proxy='example1.com,*,example2.com'
OK there is no sense of doing that but it has no reason not to work !?
support of IP range (e.g 10.0.0.0/24) might be also good !
maybe the better would the to
-split the content the of no_proxy variable
-iterate over each splitted string
----remove blankspace at the beginning and the end
----check for forbbiden character (report as warning and ignore ?)
----recognize IP address and also IP address range
----append one (or many in case of IP range) to the bypass_hosts attribute of ProxyInfo class
-replace the by_pass_host method by using a unix-style regex (maybe glob library ?)
The text was updated successfully, but these errors were encountered: