Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions content/doc/book/managing/cli.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -220,11 +220,17 @@ Summaries of other general options can be displayed by running the client with n
=== Client connection modes

There are three basic modes in which the client may be used, selectable by global option:
`-http`, `-webSocket`, and `-ssh`.
`-webSocket`, `-http` and `-ssh`.

==== WebSocket connection mode

This is the default mode, though you may pass the `-webSocket` option explicitly for clarity.
The advantage is that a more standard transport is used, avoiding problems with many reverse proxies or the need for special proxy configuration.

==== HTTP connection mode

This is the default mode, though you may pass the `-http` option explicitly for clarity.
Starting from Jenkins 2.391, the default mode is `-webSocket`.
To use the HTTP mode, you must explicitly pass the `-http` option.

Authentication is preferably with an `-auth` option, which takes a `username:apitoken` argument.
Get your API token from `/me/configure`:
Expand Down Expand Up @@ -275,12 +281,6 @@ This mode is known to not work reliably or at all when using certain reverse pro
Prefer WebSocket mode.
====

==== WebSocket connection mode

In Jenkins 2.217 and above, the `-webSocket` mode may be used as an alternative to `-http`.
The advantage is that a more standard transport is used,
avoiding problems with many reverse proxies or the need for special proxy configuration.

==== SSH connection mode

Authentication is via SSH keypair.
Expand Down