Skip to content

docs(sql): fix SSL option shape — sslmode goes on URL, tls takes TLSOptions - #31016

Closed
robobun wants to merge 4 commits into
mainfrom
farm/95244a01/fix-sql-ssl-docs
Closed

robobun wants to merge 4 commits into
mainfrom
farm/95244a01/fix-sql-ssl-docs

Conversation

@robobun

@robobun robobun commented May 18, 2026 •

Copy link
Copy Markdown
Collaborator

Problem

The Connection Options examples at https://bun.sh/docs/runtime/sql#mysql-options show:

// SSL/TLS options
ssl: "prefer", // or "disable", "require", "verify-ca", "verify-full"

But the ssl/tls option keys only accept boolean | TLSOptions | Bun.BunFile — the SSL mode string is selected via the ?sslmode= query parameter on the connection URL, not via an options key.

Passing ssl: "verify-full" as a string silently falls through to prefer mode (any truthy tls bumps the default disable up to prefer at shared.ts:849). A user following the old docs would get a weaker mode than they asked for, with no error.

Fix

  • Rewrite the MySQL Connection Options example to use tls: true and point at the SSL Modes section for mode selection.
  • Rewrite "SSL Modes Overview" to show sslmode= on the URL as the single supported way to pick a mode. Correct the default (disable, not prefer). Replace the "Using With Connection Strings" subsection with "Customizing The TLS Configuration" that demonstrates tls: {...} + URL sslmode= composed together.
  • Fix the URL example ?ssl=true (which isn't parsed as a TLS toggle and becomes a no-op connection parameter) to ?sslmode=require.

Tests

Added an SSL mode and TLS option parsing describe block to test/js/sql/adapter-env-var-precedence.test.ts pinning the runtime behavior the new docs promise:

  • Each ?sslmode=<mode> on the URL resolves to the correct SSLMode enum value.
  • sslMode defaults to disable when nothing is set.
  • tls: true and tls: { ... } both coerce sslMode to prefer.
  • sslmode=verify-full on the URL combined with tls: { rejectUnauthorized: true } produces the combined shape with sslMode = verify_full.
  • The ssl option is an exact alias for tls.
  • ?sslmode=bogus throws.
49 pass
 0 fail
139 expect() calls

Fixes #31015


no test proof · iteration 4 · Platform-specific test-only change; deferring to CI.

@coderabbitai

coderabbitai Bot commented May 18, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

This PR corrects Bun's SQL TLS/SSL configuration documentation and adds validation tests. The docs were showing an incorrect ssl: "mode" syntax; they now accurately document the tls option for configuration and sslmode URL parameter for mode selection, with examples for both MySQL and PostgreSQL. A new test suite validates the documented behavior.

Changes

SQL TLS/SSL Configuration

Layer / File(s) Summary
MySQL TLS Configuration Examples
docs/runtime/sql.mdx
Updated MySQL connection string to show sslmode=require query parameter example and options block to document TLS configuration via tls option (boolean, object, or BunFile) with mode selection via sslmode URL parameter, replacing incorrect ssl: "prefer" syntax.
PostgreSQL TLS Configuration Example
docs/runtime/sql.mdx
Updated PostgreSQL TLS object example to reference Bun.file(...) for ca, key, and cert, aligning with MySQL format.
SSL/TLS Modes Conceptual Documentation
docs/runtime/sql.mdx
Rewrote "SSL Modes Overview" section to unify PostgreSQL and MySQL concepts, centered on sslmode URL parameter for mode selection, added "Customizing The TLS Configuration" subsection with rejectUnauthorized and file-based certificate examples, and clarified that tls: true enables prefer mode while ssl is a deprecated alias.
SSL/TLS Parsing Test Suite
test/js/sql/adapter-env-var-precedence.test.ts
Added "SSL mode and TLS option parsing" test block validating sslmode URL parameter precedence, default behavior (disable mode, undefined tls), tls option coercion to prefer mode, deprecated ssl aliasing, and invalid sslmode error throwing.
🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: correcting the SQL documentation to show that sslmode goes on the URL and tls takes TLSOptions, not SSL mode strings.
Linked Issues check ✅ Passed All objectives from issue #31015 are met: docs corrected to remove SSL mode strings from ssl/tls options, sslmode= URL parameter documented as the supported way to select mode, default corrected to disable, URL examples fixed, and tests added.
Out of Scope Changes check ✅ Passed All changes in the PR are directly scoped to fixing the SSL/TLS documentation issue and adding related tests. No unrelated modifications are present.
Description check ✅ Passed The description clearly explains the problem, fix, and tests, though it uses different headings than the template.

Comment @coderabbitai help to get the list of available commands.

@robobun

robobun commented May 18, 2026 •

Copy link
Copy Markdown
Collaborator Author
Updated 1:21 AM PT - Jul 9th, 2026

❌ @robobun, your commit 278ffb4 has 5 failures in Build #70858 (All Failures):


🧪   To try this PR locally:

bunx bun-pr 31016

That installs a local version of the PR into your bun-31016 executable, so you can run:

bun-31016 --bun

Comment thread docs/runtime/sql.mdx Resolved

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — thanks for wrapping the cert paths in Bun.file(); the docs now match the actual sslmode/tls parsing in shared.ts and the new tests pin it.

Extended reasoning...

Overview

This PR touches two files: docs/runtime/sql.mdx (corrects misleading SSL/TLS examples — sslmode goes on the URL query string, tls takes boolean | TLSOptions | BunFile, default mode is disable not prefer) and test/js/sql/adapter-env-var-precedence.test.ts (adds a new describe block with 7 tests pinning the documented behavior). No runtime/production code is modified.

I verified the docs claims against src/js/internal/sql/shared.ts: the SSLMode enum values (0–4) match the test's local mirror, normalizeSSLMode throws on unknown values, the default is SSLMode.disable (line 587), ?sslmode= is the query-param key parsed (line 624), and truthy tls with sslMode === disable bumps to prefer (line 849). All new prose is accurate.

Prior feedback addressed

My earlier inline comment flagged that ca: "path/to/ca.pem" would be treated as inline PEM content rather than a file path. Commit 3ff1117 addressed this fully — the new "Customizing The TLS Configuration" example and both pre-existing commented-out blocks now use Bun.file("path/to/..."). The current bug-hunting run found no issues.

Security risks

None. This is documentation + additive tests. If anything, it reduces a security footgun by removing an example that silently downgraded ssl: "verify-full" to prefer mode.

Level of scrutiny

Low-to-medium. Docs-only changes plus additive option-parsing tests (no network I/O, no DB connections — they only inspect new SQL(...).options). No CODEOWNERS apply to these paths. The test file already had the sslMode?: number module augmentation and existing sslMode assertions, so the new tests follow established patterns.

Other factors

Tests are purely additive (new describe block at the end), 49 pass / 0 fail per the PR description, and the serverName: "localhost" assertion in the combined-mode test correctly reflects the tls = { ...tls, serverName: hostname } injection at shared.ts:843.

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — the Bun.file(...) fix in 3ff1117 addresses my earlier comment, and the new docs + tests now line up exactly with the parsing logic in shared.ts.

Extended reasoning...

Overview

This PR corrects misleading TLS/SSL documentation in docs/runtime/sql.mdx (the old example showed ssl: "prefer" as a mode-string option, which the runtime never supported) and adds a test block to test/js/sql/adapter-env-var-precedence.test.ts pinning the actual option-parsing behavior. No runtime code is touched.

Verification against implementation

I cross-checked every documented claim against src/js/internal/sql/shared.ts:

  • SSLMode const enum at L106-112 matches the test's mirrored values (disable=0 … verify_full=4).
  • sslmode URL query param is parsed via normalizeSSLMode at L624-625; invalid values throw at L140.
  • Default sslMode is disable at L587 (docs previously said prefer, now corrected).
  • tls ||= options.tls || options.ssl at L762 confirms ssl is a deprecated alias with the same shape.
  • Truthy tls with sslMode === disable coerces to prefer at L849-850.
  • serverName is injected into the tls object only when sslMode !== disable before the prefer-coercion (L841), which is exactly what the two tls tests assert (object stays untouched for tls-only, gains serverName: "localhost" when combined with ?sslmode=verify-full).

My prior inline comment about ca/key/cert strings being PEM content rather than file paths was addressed in 3ff1117 — all three example blocks (the new active one and the two pre-existing commented ones) now use Bun.file(...).

Security risks

None. This is a documentation correction plus read-only assertions on option parsing. If anything, it reduces a security footgun by removing an example that silently downgraded verify-full requests to prefer.

Level of scrutiny

Low. Docs-only change with additive tests; no runtime/native code modified. Neither file falls under a CODEOWNERS rule.

Other factors

The new tests follow the existing patterns in the file (inspecting new SQL(...).options), reuse the existing env-scrubbing beforeEach, and the PR description reports 49 pass / 0 fail. CodeRabbit found nothing actionable. The bug-hunting system found no issues on this revision.

@robobun

robobun commented May 19, 2026

Copy link
Copy Markdown
Collaborator Author

Docs-only diff. Tests pass 49/49 locally (USE_SYSTEM_BUN=1 bun test test/js/sql/adapter-env-var-precedence.test.ts).

CI has been red on unrelated lanes across three runs, each a different fingerprint my diff cannot plausibly affect:

  • Build #55910 (6c4b3ff): x64-musl / aarch64-musl build-bun failures in scripts/build/ci.ts
  • Build #55912 (3ff1117): ubuntu-25-x64-test-bun + debian-13-x64-asan-test-bun
  • Build #55925 (d78fcec, empty ci: retrigger): darwin-14-x64 / darwin-14-aarch64 / darwin-26-aarch64 "Expired"

The diff between 6c4b3ff ↔ 3ff1117 ↔ d78fcec is three doc lines and a retrigger — no test or src change — yet each run failed on a completely different set of lanes. That's infra, not this PR.

Used my one re-roll on d78fcec. Needs a maintainer to merge.

@robobun
robobun force-pushed the farm/95244a01/fix-sql-ssl-docs branch from d78fcec to 951b467 Compare June 30, 2026 04:32
@mintlify

mintlify Bot commented Jun 30, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
bun 🟢 Ready View Preview Jun 30, 2026, 4:34 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@robobun

robobun commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator Author

Rebased onto origin/main and force-pushed (951b467).

One conflict in docs/runtime/sql.mdx (SSL Modes Overview): main had reworded the section but kept the buggy ssl: "disable" string example. Took this PR's version, which replaces it with the sslmode= URL guidance.

While rebasing I also found the runtime TLS coercion changed on main (#31495): an explicit tls/ssl option now requires an encrypted connection (require) instead of prefer, and a ca or rejectUnauthorized: true escalates to verify-full. That broke two of the option-parsing tests I added. I updated the docs (tls: true -> require, with a note on the verify-full escalation) and the tests to assert the new behavior, and added two cases covering the verify-full escalation.

Tests: 51 pass / 0 fail (USE_SYSTEM_BUN=1 bun test test/js/sql/adapter-env-var-precedence.test.ts).

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — verified the rebased docs and tests match the current shared.ts TLS coercion (require-by-default, ca/rejectUnauthorized → verify-full); the only finding is a comment-length nit.

Extended reasoning...

Overview

This PR corrects docs/runtime/sql.mdx to stop documenting the unsupported ssl: "<mode>" string syntax and instead point users at the ?sslmode= URL parameter for mode selection and tls: boolean | TLSOptions | BunFile for transport configuration. It also adds an SSL mode and TLS option parsing describe block to test/js/sql/adapter-env-var-precedence.test.ts that pins the option-parsing behavior. No runtime/source code is touched.

Verification against runtime

I cross-checked every claim in the new prose against src/js/internal/sql/shared.ts at HEAD:

  • sslmode is read from the URL query at L1795-1796 and normalized via normalizeSSLMode (throws on unknown values, L147).
  • Default with no URL mode and no tls is SSLMode.disable (L1758, L886).
  • A truthy tls with sslMode === disable is bumped to require at L2038-2039.
  • An object tls with rejectUnauthorized: true, or a ca (absent an explicit rejectUnauthorized: false), escalates to verify_full at L2020-2023.
  • ssl is read as a fallback for tls at L1941.

Each new test case lines up with that logic, including the serverName injection at L2026-2029 (only applied once sslMode !== disable, which is why the { rejectUnauthorized: false } case correctly expects no serverName). The post-rebase update for #31495 (prefer → require, plus the verify-full escalation) is reflected in both the prose and the assertions.

Security risks

None introduced. This is documentation plus read-only option-parsing assertions; it tightens user guidance toward stronger TLS modes (the old docs silently degraded "verify-full" to a weaker mode). No auth, crypto, or permission code paths are modified.

Level of scrutiny

Low. Docs + tests only, no src/ changes, no CODEOWNERS on these paths. My earlier review caught the ca: "path/to/ca.pem" string-vs-PEM issue and the author fixed all three occurrences (now Bun.file(...)). The single remaining finding is a CLAUDE.md style nit about an 8-line explanatory comment above the test block — non-blocking and posted inline.

Other factors

The author reports 51/51 pass locally after the rebase; prior CI redness was unrelated infra flake across disjoint lanes. Nothing outstanding from human reviewers.

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — docs now match the actual shared.ts TLS coercion, and the new option-parsing tests pin it.

Extended reasoning...

Overview

This PR touches two files: docs/runtime/sql.mdx (corrects the SSL/TLS configuration examples and prose) and test/js/sql/adapter-env-var-precedence.test.ts (adds a new describe block with ~10 option-parsing tests). No runtime/source code is modified. I traced every documented claim and every new test assertion against src/js/internal/sql/shared.ts — the SSLMode enum values, the ?sslmode= URL parsing at L1795-1796, the disable default at L1758, the tls → require coercion at L2038-2040, the ca/rejectUnauthorized: true → verify_full escalation at L2020-2023, the serverName injection at L2026-2029, the ssl → tls alias at L1941, and the invalid-mode throw at L147 — and all of them line up exactly with what the docs and tests now state.

Security risks

None introduced. The change is a net security improvement: the previous docs told users to pass ssl: "verify-full" as a string, which silently degraded to a weaker mode. The corrected docs steer users to ?sslmode= (which actually works) and Bun.file() for cert material (so PEM paths aren't misparsed as inline content). No auth, crypto, or permission code paths are touched.

Level of scrutiny

Low. This is a documentation correction plus additive, non-network test cases that only exercise the synchronous option parser (new SQL(...).options) — they don't open connections. Neither file is covered by CODEOWNERS.

Other factors

Both of my prior inline comments (the Bun.file() wrapping and the 8-line comment-block nit) were addressed in 30be0dd / 2310f8b and are marked resolved. The bug-hunting pass on the current revision found nothing. CodeRabbit had no actionable findings. The author already noted CI flakes on unrelated lanes are infra noise; the relevant test file passes 51/0 locally per their report, and the assertions match the source as I read it.

@robobun

robobun commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator Author

CI (build #67124, rebased 2310f8b) failed on three Windows tests unrelated to this diff:

  • test/cli/install/bun-install.test.ts (win 2019 x64-baseline) — EBADF: bad file descriptor during a registry install
  • test/cli/update_interactive_install.test.ts (win 2019 x64) — interactive install exit code, recovered on retry
  • test/js/bun/spawn/spawn-pipe-leak.test.ts (win 11 aarch64) — memory-leak threshold, recovered on retry

This PR changes only docs/runtime/sql.mdx and adds a synchronous option-parsing test (new SQL(...).options, no connections). It touches no install/spawn/update code and no Windows path, and Bun runs each test file in its own process, so it cannot affect those suites. All three files predate this PR on main.

Across this PR's life the red lanes have been disjoint each run (x64-musl build, ubuntu-25/debian-asan, darwin timeouts, now Windows install/spawn), which is the signature of infra flake rather than a regression here. The SQL option-parsing suite passes 51/0 locally (USE_SYSTEM_BUN=1 bun test test/js/sql/adapter-env-var-precedence.test.ts).

Re-roll already spent earlier in this PR, so not pushing another. Ready for a maintainer to merge.

robobun and others added 3 commits July 9, 2026 04:55
…ptions

The MySQL and Postgres `Connection Options` examples showed
`ssl: "prefer"` with a string literal, implying that the options object
accepts an SSL mode string. It doesn't: the `ssl`/`tls` keys only take
`boolean | TLSOptions | BunFile`, and the mode selector is the `sslmode`
query parameter on the connection URL.

Passing `ssl: "verify-full"` as a string silently coerces to `prefer`
mode (because any truthy `tls` bumps the default `disable` up to
`prefer`), so a user following the old docs would get a weaker mode than
requested with no error.

- Rewrite the MySQL options example to use `tls: true` and point at the
  SSL Modes section for mode selection.
- Rewrite the "SSL Modes Overview" to show `sslmode=` on the URL as the
  single supported way to pick a mode, add a "Customizing The TLS
  Configuration" subsection for `tls: {...}`, and correct the default
  (it's `disable`, not `prefer`).
- Fix the URL-form example that used `?ssl=true` (which isn't parsed as
  a TLS toggle) to use `?sslmode=require`.
- Pin the runtime behavior the new docs promise with unit tests in
  test/js/sql/adapter-env-var-precedence.test.ts: sslmode values parse to
  the expected enum, default is disable, `tls: true`/object coerces to
  prefer, and URL sslmode + tls object compose correctly.

Fixes #31015
In Bun.TLSOptions, string values for ca/key/cert are interpreted as
inline PEM content, not file paths — only Bun.file() triggers a file
read. Update the new verify-full example (and the pre-existing
commented-out blocks it sits next to) to use Bun.file() so a user
copying the example actually loads the cert from disk instead of
handing BoringSSL the literal string 'path/to/ca.pem' as PEM.
After rebasing onto main, the TLS mode coercion changed (#31495): an
explicit tls/ssl option now requires an encrypted connection (`require`)
instead of `prefer`, and supplying a `ca` or `rejectUnauthorized: true`
escalates to `verify-full`. Update the docs that claimed `tls: true`
enables `prefer` mode, and update the option-parsing tests to assert the
new require/verify-full behavior (plus two new cases covering the
verify-full escalation).
@robobun
robobun force-pushed the farm/95244a01/fix-sql-ssl-docs branch from 2310f8b to 25ba803 Compare July 9, 2026 04:55
@robobun

robobun commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator Author

Rebased onto main again (25ba803). Same single conflict as last time in the SSL Modes section (main still had the ssl: "disable" string example); took this PR's sslmode= URL version. Tests: 51 pass / 0 fail.

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — docs now match runtime behavior, prior feedback addressed; the two remaining inline comments are test-quality nits, not blockers.

Extended reasoning...

Overview

This PR touches two files: docs/runtime/sql.mdx (rewrites the SSL/TLS configuration guidance for Bun.SQL to correctly show that sslmode= goes on the URL and tls takes boolean | TLSOptions | BunFile, not a mode string) and test/js/sql/adapter-env-var-precedence.test.ts (adds a synchronous option-parsing test suite pinning the documented behavior). No runtime source is modified.

Security risks

None introduced. This is documentation about TLS configuration, not code implementing it. The change is a strict security improvement: the old docs told users ssl: "verify-full" selected verify-full mode when it actually fell through to a weaker mode. The new prose correctly describes the require/verify-full escalation semantics, and the added tests pin those semantics against shared.ts. My earlier review caught one security-misleading example (ca: "path/to/ca.pem" as a string vs Bun.file(...)) and it was fixed; I re-verified all three affected blocks now use Bun.file().

Level of scrutiny

Low-to-moderate. Docs + test-only with no compiled-code surface, so no runtime regression risk. The prose is security-adjacent, which normally raises the bar, but the tests added in this PR mechanically verify every claim the new prose makes (each sslmode= value, the disable default, tls: true → require, ca/rejectUnauthorized: true → verify-full, ssl alias, invalid mode throws), so the docs are demonstrably aligned with runtime behavior rather than asserted by hand.

Other factors

I've reviewed this PR twice before; both prior comments (the Bun.file() wrapping and the 8-line comment block) were addressed and resolved. The only change since my last review is a mechanical rebase re-resolving the same docs conflict. The two findings from this run — a vacuous "sslmode wins" test name and a bare .toThrow() — are explicitly nits about test assertion strength, not correctness, and don't block. No CODEOWNERS on the touched paths.

Replace the combine test (whose inputs both independently produced
verify-full, so neither path's regression could fail it) with two
conflicting-input cases: a verify-ca URL mode survives a verifying tls
object, and a require URL mode is escalated by one. Pin the invalid
sslmode error message instead of a bare toThrow().

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — both remaining nits addressed in 278ffb4.

Extended reasoning...

Overview

This PR corrects the SQL SSL/TLS documentation in docs/runtime/sql.mdx and adds a test suite in test/js/sql/adapter-env-var-precedence.test.ts pinning the documented behavior. No runtime code is modified — only docs and tests.

The docs previously showed ssl: "prefer" (a mode string on the options object), which the runtime does not support; the fix documents the actual API: sslmode= on the connection URL selects the mode, and tls on the options object takes boolean | TLSOptions | BunFile. Three pre-existing commented-out examples were also corrected to wrap cert paths in Bun.file().

Security risks

None. No runtime, auth, crypto, or TLS handshake code is touched — this is documentation describing existing behavior plus synchronous option-parsing tests that never open a connection. The docs change is a net security improvement (the old example silently degraded verify-full to a weaker mode).

Level of scrutiny

Low. Docs + additive tests only. I verified every claim in the new prose and every test assertion against src/js/internal/sql/shared.ts (lines 113-147, 1947, 2026-2045): the SSLMode enum values, the ssl → tls alias, the tls: true → require coercion, the ca/rejectUnauthorized: true → verify_full escalation, the sslMode < verify_ca guard, the serverName injection, and the ERR_INVALID_ARG_VALUE message — all match.

Other factors

This is my fourth pass on this PR. All prior feedback has been addressed: the Bun.file() wrapping (3ff1117), the comment-length nit (2310f8b), and both nits from my last review — the vacuous "sslmode wins" test was replaced with two conflicting-input cases, and the bare .toThrow() now asserts the specific error message (278ffb4). The bug-hunting system found nothing on this revision. Tests are hermetic (no network, no subprocess) and follow existing patterns in the file.

@robobun

robobun commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator Author

Build #70858: the test/js/sql/postgres-invalid-message-length.test.ts failure (win11-aarch64) looks adjacent to this PR but is not: it got ERR_POSTGRES_CONNECTION_REFUSED, meaning the test's in-process mock server refused the TCP connection before the protocol check ran — a socket flake on that lane. This PR has no src changes (docs + one separate test file), so it cannot affect wire-protocol error codes. The other three failures are the same recurring Windows/ASAN install flakes as previous builds. Still ready for a maintainer.

@robobun

robobun commented Aug 14, 2026

Copy link
Copy Markdown
Collaborator Author

Closing as superseded: the runtime was changed in #37669 instead (ssl/tls now accept the mode strings and ?ssl= on the URL is honored), so the docs as they stand are accurate and this rewrite no longer applies.

@robobun robobun closed this Aug 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MySQL options documentation incorrect for SSL settings

1 participant