Files
requests3/requests
Martijn Pieters 4decc7986e Use a JSON-specific encoding detection when no encoding has been specified.
JSON *must* be encoded using UTF-8, UTF-16 or UTF-32 (see the [RFC][1]; detect the encoding based on the fact that JSON always starts with 2 ASCII characters.

[1]: http://tools.ietf.org/html/rfc4627#section-3
2012-10-25 17:43:52 +02:00
..
2012-10-09 00:42:48 +03:00
2012-08-16 17:38:35 -04:00
2012-05-10 17:01:09 -05:00
2012-10-09 00:42:49 +03:00
2012-06-28 15:58:00 -07:00
2012-06-28 15:58:00 -07:00
2012-10-22 23:58:49 +02:00
2012-10-09 00:42:49 +03:00
2012-09-23 12:41:54 -05:00
2012-08-16 17:38:35 -04:00
2012-10-09 00:42:49 +03:00
2012-08-16 17:38:35 -04:00
2012-09-02 23:10:28 -04:00
2012-09-02 23:10:28 -04:00