- 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.
-
- 17 4月, 2020 1 次提交
-
-
由 Asher 提交于
Fixes #1535.
-
- 14 4月, 2020 1 次提交
-
-
由 Asher 提交于
Fixes #1507.
-
- 09 4月, 2020 1 次提交
-
-
由 Asher 提交于
Otherwise the request will just hang.
-
- 08 4月, 2020 1 次提交
-
-
由 Asher 提交于
The raw value is now passed back to VS Code so it can do the parsing with its own URI class rather than trying to parse using Node's url module first since that has no guarantee of working the same way. It also lets us keep the vscode-remote bit internal to VS Code. Removed the logic that keeps trying paths until it finds a valid one because it seems confusing to open a path and silently get some other path instead of an error for the one you tried to open. Now it'll just use exactly what you specified or fail trying. Fixes #1488. The problem here was that url.parse was encoding the spaces then the validation failed looking for a literal %20.
-
- 03 4月, 2020 18 次提交
-
-
由 Asher 提交于
-
由 Asher 提交于
This makes the code much more internally consistent (providers just return payloads, include the proxy provider).
-
由 Asher 提交于
-
由 Asher 提交于
There's no need to specially construct the path.
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
-
由 Asher 提交于
Otherwise they'll crash code-server.
-
由 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.
-
由 Asher 提交于
- Add type to HTTP options. - Fix certificate message always saying it was generated. - Dedent output not directly related to the HTTP server. - Remove unnecessary comma.
-
- 31 3月, 2020 4 次提交
- 28 3月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 26 3月, 2020 2 次提交
- 25 3月, 2020 1 次提交
-
-
由 Asher 提交于
-
- 23 3月, 2020 1 次提交
-
-
由 Maksim Ryzhikov 提交于
-
- 17 3月, 2020 6 次提交
- 14 3月, 2020 2 次提交