I just discovered that the requests library honors HTTP_PROXY, but does not
honor NO_PROXY.
Based on what you say below, I'm betting this is your problem, or at least
a part of it.
One solution is for you to explicitly unset HTTP_PROXY when you don't want
it.
Another is for you to specify a
Ahh!
By sheer coincidence, it was actually me that integrated the latest
SOCKS/proxy support you see in urllib3 lol.
Basically, the current proxy handling is quite badly broken and required a
bunch of fixes.
I submitted a stable set of patches for integration here;
heya,
Thanks for the tips - you're probably right, I might need to whip out
wireshark or something and see what exactly is going on.
However, one thing I did notice - I normally have the http_proxy
environment variable set, as we use a HTTP proxy at work.
However, if I unset the http_proxy
Hi Victor,
I've had my fair share of exposure with python requests - so thought I'd
chime in.
On first glance, this looks to be an issue with specifying the port number
into python-requests, doing so seems to send the entire "
http://localhost:8000/api/v1/host/?name__regex==json; as the
request.
Hi,
I have a Django app that's serving up a RESTful API using tasty-pie.
I'm using Django's development runserver to test.
When I access it via a browser it works fine, and using Curl also works
fine:
curl "http://localhost:8000/api/v1/host/?name__regex=format=json;
On the console with
5 matches
Mail list logo
