Closed fare closed 9 months ago
Name | Link |
---|---|
Latest commit | 8febe0445b769343e7ef4b9093be99ed1dd1c400 |
Latest deploy log | https://app.netlify.com/sites/elastic-ritchie-8f47f9/deploys/655c9e3883fb5f0008be88e9 |
Deploy Preview | https://deploy-preview-1044--elastic-ritchie-8f47f9.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
It looks like I'm getting closer, but I must be doing the reset wrong still, or something, because after a seemingly successful SSL negotiation (albeit in insecure context), I get:
*** ERROR IN std/db/postgresql#postgresql-connect__% --
*** ERROR IN "db/postgresql-driver.ss"@622.27-622.43 [IOError]: unexpected backend message
--- irritants: postgresql-recv! 23
23 is definitely not part of the protocol, and I don't suppose the bug is server side, so presumably my reset!
didn't do the right thing and my buffer is now out of sync. Please advise @vyzo
I had misunderstood the ssl-client-upgrade API and was simply seeing the SSL frames. Everything now OK.
netlify build failed
and CI build...
Had to fix the defaults. Works for me now. PTAL.
PTAL
CI did not run...
PTAL
Add support for SSL in PostgreSQL client