I don't know if you have solved it or not, but... I do have a problem that sounds like the one you experience. What I noticed is that when I am using GET (as one example) on an HTTP address, then the module uses both environment variable "http_proxy" and "no_proxy" (and everything works). However, when doing the same towards an https address, the module uses "https_proxy" (as expected), but it seems "no_proxy" settings aren't used. SO far I have no solution or workaround.