sproxy2, branch 1.92.0 HTTP proxy for authenticating users via OAuth2 https://git.pashev.ru/sproxy2/atom?h=1.92.0 2016-11-28T18:42:14Z Version 1.92.0 2016-11-28T18:42:14Z Igor Pashev pashev.igor@gmail.com 2016-11-28T18:42:14Z urn:sha1:e4639176a70e60d609d559f51903b492be042ec3 Allow running in plain HTTP mode (no SSL) 2016-11-28T18:24:51Z Igor Pashev pashev.igor@gmail.com 2016-11-28T18:24:51Z urn:sha1:02e85ea26fc297d41a91c91d12b3e2aa290e62ff This can be useful when Sproxy is behind some other proxy or load-balancer. sproxy.sql: add "user" table 2016-11-28T15:15:05Z Igor Pashev pashev.igor@gmail.com 2016-11-28T15:05:42Z urn:sha1:389d4b0904c718bdabbce400b8fe9a8f0fcb9f80 This will allow simple listing, removing and renaming users (changing email). It also will allow synchronizing Sproxy database with other sources. Note that this change is not compatible with current SproxyWeb, so don't try to update production databases. Speaking of synchronization, more then added, it's important that account are deleted automatically. Apply same settings to redirect server 2016-11-28T12:57:23Z Igor Pashev pashev.igor@gmail.com 2016-11-28T12:57:23Z urn:sha1:1183905204bf70e69a2c853e71efed378f05d0b9 Version 1.91.0 2016-11-26T20:04:19Z Igor Pashev pashev.igor@gmail.com 2016-11-26T20:04:19Z urn:sha1:c28980e5dd731b3d98117c301d2e51cc96c4f867 Refactored data import 2016-11-26T19:53:22Z Igor Pashev pashev.igor@gmail.com 2016-11-26T19:42:00Z urn:sha1:a3b5b7ac059e473e10749591c11aee97482b88d1 Use persistent prepared statements for PostgreSQL data source. Import should be faster from now on. Cleaned README 2016-11-26T19:53:22Z Igor Pashev pashev.igor@gmail.com 2016-11-26T19:14:12Z urn:sha1:f0f3f550c5a414e8a84e15e9a54ba86d1ae5c143 Populate permission database from a file 2016-11-26T19:53:16Z Igor Pashev pashev.igor@gmail.com 2016-11-26T18:41:59Z urn:sha1:be9b6f68a60bec0cda4b905e9311a9076f778976 Version 1.90.2 2016-11-25T21:05:54Z Igor Pashev pashev.igor@gmail.com 2016-11-25T21:05:54Z urn:sha1:33ab0b2f945b8f4995f77c3246eb3c3f1b9d6df4 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.