notoriousno
notoriousno
My original PR got deleted by shear stupidity on my part, but I probably should've discussed the issue a bit more in this ticket to begin with...Everything happens for a...
> arguments are more interesting than ``dict``s and I find that...it sometimes boxes you into fitting square pegs into rounded rect holes. I can agree but I would ask you...
Should the value be returned as `unicode` or `bytes` (as it currently does)? While it makes sense to return bytes when doing low level transactions over the wire but it...
Ping! I'm sure everyone thinks this is issue is an inconvenience, so let's do something about it. Also, has this issue been raised in Twisted?
@glyph is it a good idea for klein :) ? For low level wire protocols it's totally reasonable for data to be `bytes` however HTTP is not low level protocol...
Fair enough. In the same vein as `treq`, I think there's some value in providing high level wrappers in `klein` as well. All I'm trying to say is, it would...
@cwaldbieser, treq and twisted developers. The HTTP Over SSL example is broken and doesn't work as written. An `Agent` doesn't take `optionsForClientTLS` as the `contextFactory` parameter, instead it should take...
The whitelisting option is the most sensible. As @twm said, it is close to what browsers do. This issue will keep coming up until a "do not validate" function is...