sproxy2/src/Sproxy/Application/OAuth2, branch master HTTP proxy for authenticating users via OAuth2 http://git.pashev.ru/sproxy2/atom?h=master 2019-09-06T16:34:43Z Reformat with modern hindent 5.2.7 2019-09-06T16:34:43Z Igor Pashev pashev.igor@gmail.com 2019-09-06T16:34:28Z urn:sha1:6df3894131699a3a81e5e4da1565268eb01639c6 Format with hindent 2017-08-06T16:50:58Z Igor Pashev pashev.igor@gmail.com 2017-08-06T16:50:58Z urn:sha1:ad1134ad752bbcd678cfb5a80217fabe57fdcd35 Fix POST requests for tokens 2017-08-06T16:22:28Z Igor Pashev pashev.igor@gmail.com 2017-08-06T16:22:28Z urn:sha1:016ef10b0a429d7c2b0c7d83914316f2211cc36b Really use application/x-www-form-urlencoded instead of query paramaters. Apparently, Google and LinkedIn are too tolerant. Yandex is not. Add Yandex 2017-08-06T16:11:48Z Igor Pashev pashev.igor@gmail.com 2017-07-26T18:11:18Z urn:sha1:671005e91e724c7f956cad24305603505e1bd322 https://tech.yandex.com/oauth/ Make sure all HTTP headers are UTF8-encoded 2016-11-25T20:51:25Z Igor Pashev pashev.igor@gmail.com 2016-11-25T20:40:29Z urn:sha1:ea17e9c2a3350ba670f95a6fa0ce7716adfa4176 Especially X-Family-Name, X-Given-Name. Since we get all the data from JSON and JSON is in UTF8 by default RFC 7159, we are safe. Refactored to make it less error-prone and to get as small number of encoding/decoding as possible. Initial release (1.90.0) 2016-11-19T20:29:43Z Igor Pashev pashev.igor@gmail.com 2016-10-27T19:57:34Z urn:sha1:4a9f329a6ea9bfa03352ca0d9dd1d556b93bec36