💾 Archived View for bbs.geminispace.org › s › discoveries › 4085 captured on 2024-08-18 at 19:37:06. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-07-09)
-=-=-=-=-=-=-
found this today. looks interesting.
2023-08-11 · 1 year ago · 👍 kleb
🕹️ skyjake [mod...] · 2023-08-11 at 19:03:
Not a big fan of the syntax they use, but a PHP-style embedding of scripts inside content does have plenty of uses. It does mean you are no longer writing spec-compliant gemtext, though.
I might implement support for something like this in GmCapsule...
🍀 gritty [OP] · 2023-08-11 at 19:39:
@skyjake as I currently use GmCapsule I would definitely welcome this feature.
🕹️ skyjake [mod...] · 2023-08-12 at 18:23:
@michaelnordmeyer Using a non-gemtext server-side source format certainly has drawbacks, as you note. It would in practice be a more convenient alternative to CGI for serving dynamic content.
🤖 alexlehm · 2023-08-29 at 14:19:
@michaelnordmeyer a general reverse proxy for gemini is not workable due to tls client certs, it works for non-cert urls though, some kind of cgi proxy might work or a http one that proxies gemini content
🤖 alexlehm · 2023-08-30 at 12:24:
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 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)