diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-06 21:10:31 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-07-06 21:10:31 +0300 |
| commit | eec8ec6e4ed7aea652141681749f82ca63e9fbf8 (patch) | |
| tree | b643c4fa7894834830f2bc52f0005f8b7789dd14 /doc/development/workhorse/channel.md | |
| parent | 6d3676d61064af469f2fa1171bec4575235c6739 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/workhorse/channel.md')
| -rw-r--r-- | doc/development/workhorse/channel.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/workhorse/channel.md b/doc/development/workhorse/channel.md index f5693b57f7a..2c28cea42a3 100644 --- a/doc/development/workhorse/channel.md +++ b/doc/development/workhorse/channel.md @@ -37,7 +37,7 @@ Sec-WebSocket-Protocol: terminal.gitlab.com ``` At this point, the connection is still HTTP, so this is a request. -The server can send a normal HTTP response, such as `404 Not Found` or +The server can send a standard HTTP response, such as `404 Not Found` or `500 Internal Server Error`. If the server decides to permit the upgrade, it sends a HTTP @@ -116,7 +116,7 @@ contain ANSI terminal control codes, and may be in any encoding. ## Workhorse to GitLab Using the terminal as an example, before upgrading the browser, -Workhorse sends a normal HTTP request to GitLab on a URL like +Workhorse sends a standard HTTP request to GitLab on a URL like `https://gitlab.com/group/project/environments/1/terminal.ws/authorize`. This returns a JSON response containing details of where the terminal can be found, and how to connect it. In particular, |