Skip to content

Fixed document. #435

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 24, 2025
Merged

Fixed document. #435

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 1 addition & 5 deletions doc/modules/ROOT/pages/tool/trial.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,9 @@ You can connect to the broker `async-mqtt.redboltz.net` for testing.
|10443|MQTT on Websocket(TLS, verify_peer)|./client_cli.sh --host async-mqtt.redboltz.net --port 10443 --protocol wss
|===

* verify_peer: If a client prepare to send Client Certificate, the broker verify it.
* verify_none: Even if a client prepare to send Client Certificate, the client doesn't send it during TLS handshaking.
** If a browser find Client Certificates, direct accessing to wss:// would error. See https://github.com/redboltz/async_mqtt/pull/433 This setting can avoid the error.

* verify_peer: If a client is prepared to send a client certificate, the broker will verify it.
* verify_none: Even if a client is prepared to send a client certificate, it will not be sent during the TLS handshake.
* If a browser detects available client certificates, directly accessing. See https://github.com/redboltz/async_mqtt/pull/433 . This setting prevents that error.
** If a browser detects available client certificates, directly accessing. See https://github.com/redboltz/async_mqtt/pull/433 . This setting prevents that error.

== Important notice

Expand Down