I've added stripe to the whitelist, but unfortunately it looks like the stripe client won't work:
APIError: Invalid response body from API: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>ERROR: The requested URL could not be retrieved</title> <style type="text/css"><!-- %l body :lang(fa) { direction: rtl; font-size: 100%; font-family: Tahoma, Roya, sans-serif; float: right; } :lang(he) { direction: rtl; float: right; } --></style> </head><body> <div id="titles"> <h1>ERROR</h1> <h2>The requested URL could not be retrieved</h2> </div> <hr> <div id="content"> <p>The following error was encountered while trying to retrieve the URL: <a href="https://api.stripe.com/v 1/account">https://api.stripe.com/v1/account</a></p> <blockquote id="error"> <p><b>Unsupported Request Method and Protocol</b></p> </blockquote> <p>Squid does not support all request methods for all access protocols. For example, you can not POST a Gopher request.</p> <p>Your cache administrator is <a href="mailto:webmaster%W">webmaster</a>.</p> <br> </div> <hr> <div id="footer"> <p>Generated Fri, 12 Apr 2013 15:43:26 GMT by giles-liveproxy (squid/2.7.STABLE9)</p> <!-- ERR_UNSUP_REQ --> </div> </body></html> (HTTP response code orwas 501)
Unfortunately we've found that not all HTTPS client libraries work well with our proxy server -- IIRC urllib3
doesn't work either.
So, that means anyone that wants to use stripe is going to have to upgrade to a paid-for account... but then again, if you're talking to a credit card processor, hopefully you can afford it :)