💾 Archived View for gemi.dev › gemini-mailing-list › 000603.gmi captured on 2024-03-21 at 17:54:32. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-12-28)
-=-=-=-=-=-=-
Hello all, since a desire for this was expressed, I have adapted the agate gemini server to do proxying instead[1]. It is intended to be run on port 80. You can still run a web server on the standard 443 port, in fact the server will try to redirect HTTP requests to the HTTPS version of the website (it just spits out some HTTP response if the TLS connection cannot be established as an assumption). The certificate policy is very weak, it will simply accept any certificate. I think that is the laziest and easiest solution, while of course a major flaw. If you know better, you are welcome to submit a patch/open a pull request. I am running a demo on my own VPS, for some basic instructions you can go to <gemini://qwertqwefsday.eu:80/>.[2] And you'll have to find a client that can make use of proxying if you really want to try it. I did some rudimentary tests, but am not sure how well it works. If you encounter issues, feel free to reach out to me (or open an issue/pull request on GitHub[1]). Johann [1] <https://git.qwertqwefsday.eu/index.cgi/agateway.git> ??? <https://github.com/Johann150/agateway> [2] In the hope that this email will not cause it to melt. If it is down when ??? you try, there is probably some problem with it and I am already on it. ?? ?I'm not sure how long I'll keep the service up. --- You can verify the digital signature on this email with the public key available through web key discovery. Try e.g. `gpg --locate-keys`... -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210104/e4f3 7161/attachment-0001.sig>
---
Previous Thread: [Tech] Useless statistics of the day: status codes