Ensure sslmode=disable is respected #268
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It appears that
crystal-pg
is not compatible with PostgreSQL instances that do not have SSL support, and it seems to be ignoring thesslmode=disable
parameter. This issue is particularly evident with PostgreSQL databases provisioned in Fly.io since they are accessed over an encrypted internal network, and SSL is not supported in such cases (ref).To illustrate, I was trying to make this seemingly simple script work:
And I got the following trace:
Trace
It should be noted that while I was testing this, the
DATABASE_URL
environment variable was complying to the following format:postgres://<user>:<pwd>@<host>:<port>/<db>?sslmode=disable
.This seems to indicate that
crystal-pg
is trying to require an SSL connection when it shouldn't.In this pull request, I am providing a fairly simple fix to this. Let me know if I am missing something or if this is not the right way to go about this!