mirror of
https://github.com/supabase/supabase.git
synced 2026-10-13 13:19:09 +03:00
Marcus Weinerandsupabase-vercel-tedd[bot]
8c10701cb5
## Problem We're soon going to remove CBC-mode ciphers from the HTTP APIs for projects hosted on the platform. ## Solution These docs help customers understand what our TLS offering looks like and helps with the change. ## Review instructions Check the copy if it's understandable and well written ## Checklist Check all before review: - [x] I have read [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) - [x] If I wrote a new docs topic or edited an existing topic, I used the `/write-the-docs` or `/edit-the-docs` skill, which applies the docs [style guide](https://github.com/supabase/supabase/tree/master/apps/docs/style-guide) The `/write-the-docs` skill showed these notes: - The error strings in the troubleshooting table are typical messages, not taken from Supabase logs or tickets. - The proxy workaround is my suggestion, not part of the approved comms. - The openssl command appears on both pages. The troubleshooting renderer (MDXRemoteBase) doesn't seem to support <$Partial>, and no troubleshooting article uses one, so I didn't share it. - Both pages describe a future removal. After November 10 the wording ("will remove", "until the removal date") needs a follow-up edit to present tense. --------- Co-authored-by: supabase-vercel-tedd[bot] <336548405+supabase-vercel-tedd[bot]@users.noreply.github.com>