You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some libSQL documentation shows connections being set up using the libsql URL scheme. For example, someone reading the Turso docs could easily come across their Spin tutorial and think, "aha, that's how I should set up my runtime config."
However, the HTTP client that Spin uses rejects this prefix (or did when I used it, though we have revved since), and expects only a host name. If a user provides a libsql:// URL in their runtime config, Spin will error on it.
The draft docs do warn people to specify only the host name. However, we should consider being more forgiving in Spin, and automatically stripping the libsql:// prefix if present.
A potential risk is if we later do have a reason to support the libsql:// scheme and need a way to disambiguate the protocols.
The text was updated successfully, but these errors were encountered:
Some libSQL documentation shows connections being set up using the
libsql
URL scheme. For example, someone reading the Turso docs could easily come across their Spin tutorial and think, "aha, that's how I should set up my runtime config."However, the HTTP client that Spin uses rejects this prefix (or did when I used it, though we have revved since), and expects only a host name. If a user provides a
libsql://
URL in their runtime config, Spin will error on it.The draft docs do warn people to specify only the host name. However, we should consider being more forgiving in Spin, and automatically stripping the
libsql://
prefix if present.A potential risk is if we later do have a reason to support the
libsql://
scheme and need a way to disambiguate the protocols.The text was updated successfully, but these errors were encountered: