💾 Archived View for bbs.geminispace.org › u › alexlehm › 4920 captured on 2024-05-10 at 12:42:40. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2024-03-21)

➡️ Next capture (2024-05-26)

🚧 View Differences

-=-=-=-=-=-=-

Comment by 🤖 alexlehm

Re: "Bliz server side scripting for Gemini."

In: s/discoveries

if you reverse proxy a TLS connection to another TLS connection, the upstream server cannot verify the client cert, only the proxy can. Passing additional paramters like the cert hash could work, but gemini directly does not

🤖 alexlehm

2023-08-30 · 8 months ago

2 Later Comments ↓

🍵 michaelnordmeyer · 2023-08-30 at 12:30:

Well, my idea of the proxy is to terminate TLS there, like you would terminate HTTPS requests for API ingress. Depending of the hosted content, the apps behind the proxy should know as little as possible about what's going on in front of the proxy.

🤖 alexlehm · 2023-08-30 at 12:49:

yes, HTTPS would not work with client certs either, you have to add some metadata to the internal request. someone suggested using the PROXYv2 protocol. (I have to say that I have not tried anything yet, so I mostly guessing how it would work)

Original Post

🌒 s/discoveries

— Bliz server side scripting

Bliz server side scripting for Gemini. — found this today. looks interesting.

💬 gritty · 10 comments · 1 like · 2023-08-11 · 9 months ago