Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2017-05-15 | Version 1.95.01.95.0 | Igor Pashev | 2 | -1/+9 | |
2017-05-13 | Respond with 502 on every backend exception | Igor Pashev | 1 | -2/+6 | |
From RFC 7231: 6.6.3. 502 Bad Gateway The 502 (Bad Gateway) status code indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request. | |||||
2017-05-13 | Add end-point for checking access in a bunch | Igor Pashev | 5 | -36/+140 | |
2017-04-20 | ChangeLog: updated link | Igor Pashev | 1 | -1/+1 | |
2017-02-07 | Version 1.94.11.94.1 | Igor Pashev | 2 | -1/+8 | |
2017-02-07 | Oops ¯\_(ツ)_/¯ | Igor Pashev | 1 | -1/+1 | |
2017-01-30 | Version 1.94.01.94.0 | Igor Pashev | 2 | -1/+16 | |
2017-01-15 | README: replace HTTP Basic authentication | Igor Pashev | 1 | -1/+3 | |
2017-01-03 | Typo | Igor Pashev | 1 | -1/+1 | |
2016-12-27 | Disregard possible port in the Host HTTP header | Igor Pashev | 2 | -13/+16 | |
Motivation: to make it easy to switch Sproxy's primary port. This could be useful when running private (behind Sproxy) and public (e. g. nginx) HTTPS services on the same server. In such a setup one can use port 443 for public services and alt. HTTPS port 8443 for Sproxy. Before this change, Sproxy took possible port number into account when looking for backend and privileges. Now it ignores port and considers domain name only. This also gets Sproxy in line with browsers and SSL certificates: certificates do not include port numbers, browsers ignore ports when sending cookies. | |||||
2016-12-27 | Suggest alternative HTTPS port 8443 | Igor Pashev | 1 | -1/+4 | |
2016-12-18 | BREAKING: no wildcards for domain names | Igor Pashev | 2 | -3/+3 | |
This feature was ambiguous (in the same way as paths are) and never used anyway. | |||||
2016-12-18 | sproxy.sql: updated example | Igor Pashev | 1 | -1/+4 | |
SQL wildcards are no longer supported for HTTP methods | |||||
2016-12-14 | Typo | Igor Pashev | 1 | -1/+1 | |
2016-12-13 | Version 1.93.01.93.0 | Igor Pashev | 2 | -1/+12 | |
2016-12-10 | Examples: removed yaml markers | Igor Pashev | 2 | -9/+0 | |
They don't make much sense in files. | |||||
2016-12-05 | datafile.yml.example -> datafile.example.yml | Igor Pashev | 3 | -2/+2 | |
2016-12-05 | sproxy.yml.example -> sproxy.example.yml | Igor Pashev | 3 | -2/+2 | |
2016-12-01 | BREAKING: Allow !include in config file | Igor Pashev | 3 | -25/+16 | |
This changes semantics of these options: - key - oauth2.<provider>.client_secret They are no longer files, but strings. To read content from files, use !include. The point of being files or read from files is to segregate secrets from non-sensitive easily discoverable settings. With !include it is much more simple and flexible. | |||||
2016-11-30 | Restructured README.md | Igor Pashev | 1 | -11/+11 | |
2016-11-29 | Typo | Igor Pashev | 1 | -1/+1 | |
2016-11-28 | Version 1.92.01.92.0 | Igor Pashev | 2 | -1/+14 | |
2016-11-28 | Allow running in plain HTTP mode (no SSL) | Igor Pashev | 3 | -27/+73 | |
This can be useful when Sproxy is behind some other proxy or load-balancer. | |||||
2016-11-28 | sproxy.sql: add "user" table | Igor Pashev | 1 | -6/+11 | |
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. | |||||
2016-11-28 | Apply same settings to redirect server | Igor Pashev | 1 | -7/+7 | |
2016-11-26 | Version 1.91.01.91.0 | Igor Pashev | 2 | -1/+10 | |
2016-11-26 | Refactored data import | Igor Pashev | 1 | -63/+54 | |
Use persistent prepared statements for PostgreSQL data source. Import should be faster from now on. | |||||
2016-11-26 | Cleaned README | Igor Pashev | 1 | -7/+0 | |
2016-11-26 | Populate permission database from a file | Igor Pashev | 8 | -45/+234 | |
2016-11-26 | Version 1.90.21.90.2 | Igor Pashev | 2 | -1/+15 | |
2016-11-25 | Make sure all HTTP headers are UTF8-encoded | Igor Pashev | 7 | -49/+94 | |
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. | |||||
2016-11-25 | /.sproxy/logout just redirects if no cookie | Igor Pashev | 1 | -20/+20 | |
2016-11-24 | Disable printing exceptions | Igor Pashev | 1 | -2/+4 | |
We have our own traps and logging. | |||||
2016-11-24 | Added comments on proxying | Igor Pashev | 1 | -1/+9 | |
2016-11-23 | Differentiate exceptions | Igor Pashev | 1 | -4/+15 | |
2016-11-22 | Version 1.90.11.90.1 | Igor Pashev | 2 | -1/+15 | |
2016-11-22 | Print original headers from backends | Igor Pashev | 1 | -3/+3 | |
2016-11-21 | Remove some headers which are set automatically | Igor Pashev | 1 | -3/+6 | |
By underlying HTTP Client or WAI | |||||
2016-11-20 | Show HTTP version in logs | Igor Pashev | 1 | -0/+1 | |
2016-11-20 | Updated README.md | Igor Pashev | 1 | -29/+64 | |
2016-11-20 | oauth2 callback state: include query params | Igor Pashev | 1 | -1/+3 | |
If method of the original query is GET, redirect to original path with query parameters. Otherwise redirect to "/". Previously, when unauthenticated users click on "https://example.net/foo?bar", they are redirected to "https://example.net/foo" after authentication. Now, they will be redirected to "https://example.net/foo?bar" | |||||
2016-11-19 | Initial release (1.90.0)1.90.0 | Igor Pashev | 20 | -0/+1879 | |