When a system wide HTTPS proxy has been set Hydrator should use it instead of talking directly to the Twitter API. This could be useful in situations where access to api.twitter.com is being blocked. See the discussion at the end of #43 for some context.
Like Python requests Hydrator should probably look for HTTPS_PROXY and https_proxy.
When a system wide HTTPS proxy has been set Hydrator should use it instead of talking directly to the Twitter API. This could be useful in situations where access to api.twitter.com is being blocked. See the discussion at the end of #43 for some context.
Like Python requests Hydrator should probably look for
HTTPS_PROXYandhttps_proxy.