- 13 5月, 2020 1 次提交
-
-
由 Anmol Sethi 提交于
-
- 18 4月, 2020 1 次提交
-
-
由 Asher 提交于
See #1532 for more context. - Errored JSON requests will get back the error in JSON instead of using the status text. This seems better to me because it seems more correct to utilize the response body over hijacking the status text. The caller is expecting JSON anyway. Worst of all I never actually set the status text like I thought I did so it wasn't working to begin with. - Allow the update error to propagate for JSON update requests. It was caught to show the error inline instead of an error page when using the update page but for JSON requests it meant there was no error and no error code so it looked like it succeeded. - Make errors for failed requests to GitHub less incomprehensible. Previously they would just be the code which is no context at all.
-
- 14 4月, 2020 1 次提交
-
-
由 Asher 提交于
Fixes #1507.
-
- 09 4月, 2020 1 次提交
-
-
由 Asher 提交于
Otherwise the request will just hang.
-
- 03 4月, 2020 10 次提交
-
-
由 Asher 提交于
This makes the code much more internally consistent (providers just return payloads, include the proxy provider).
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
This simplifies the logic a bit.
-
由 Asher 提交于
The cookie will be set for the proxy domain so it'll work for all of its subdomains.
-
由 Asher 提交于
It'll be able to handle /proxy requests as well as subdomains.
-
由 Asher 提交于
This allows it to be used in subdomains.
-
由 Asher 提交于
This will be used for proxying ports.
-
- 17 3月, 2020 3 次提交
-
-
由 Will O'Beirne 提交于
-
由 Asher 提交于
-
由 Asher 提交于
-
- 14 3月, 2020 1 次提交
-
-
由 Asher 提交于
This will make it work regardless of what the current URL happens to be. Also move the telemetry setting into the options since we might as well make use of it seeing as how we have to parse it for the base path anyway.
-
- 12 3月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 03 3月, 2020 3 次提交
- 29 2月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 28 2月, 2020 2 次提交
- 25 2月, 2020 1 次提交
-
-
由 Asher 提交于
Also make it a number.
-
- 22 2月, 2020 1 次提交
-
-
由 Anmol Sethi 提交于
-
- 21 2月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 20 2月, 2020 1 次提交
-
-
由 Asher 提交于
It still won't work behind a base path, but if you're using a reverse proxy you can just redirect to HTTPS yourself. And should probably handle TLS termination there too. For sockets I just needed to add back the proxy call.
-
- 15 2月, 2020 2 次提交
-
-
由 Anmol Sethi 提交于
-
由 Asher 提交于
-
- 14 2月, 2020 2 次提交
- 06 2月, 2020 4 次提交
- 05 2月, 2020 2 次提交