💾 Archived View for rawtext.club › ~sloum › geminilist › 006349.gmi captured on 2024-03-21 at 16:27:54. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

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

<-- back to the mailing list

JetForce vs. Molly Brown Server: CGI-variable SCRIPT_NAME is not present

Frank Jüdes Frank.Juedes at linux4specialists.com

Tue Apr 13 18:56:55 BST 2021

- - - - - - - - - - - - - - - - - - - 

Thank you very much Robert!

The reason why i have not considered gemserv is that it is written in /rust/ another language to which my exposure is NULL!

And the instructions on your website scared me off: As said, i am not a rust developer and there are none of the rust tools installed on any of my machines, so i would have to install the basic rust toolchain first…

On 2021-04-13 12:54, Robert "khuxkm" Miles wrote:

Just realized I forgot to link gemserv. My bad.
[1]: https://git.sr.ht/~int80h/gemserv
Just my two cents,
Robert "khuxkm" Miles
April 13, 2021 12:52 PM, "Robert "khuxkm" Miles" <khuxkm at tilde.team> wrote:
April 13, 2021 10:50 AM, "Frank Jüdes" <Frank.Juedes at linux4specialists.com> wrote:
Hi Stephane,
Thank you very much for the update. That leaves me with three options now:
Actually there are four. :P
1. Try again to install Pythron 3.7+ on my stubborn development machine
(Oracle Lunix 7…)
2. Learn go really quickly and fork the Molly Brown server - i will
call it »the sunken Molly Brown server« in that case
3. Write my own gemini server from scratch in perl
4. Use literally any other Gemini server. gemserv[1], for instance, correctly implements PATH_INFO
(which is actually the issue here, since SCRIPT_PATH -
SCRIPT_NAME is as simple as figuring out
the base directory of the Gemini server) and SCRIPT_NAME (so you don't have to do the SCRIPT_PATH
trickery). There are others as well.
It really looks like only Molly Brown and JetForce have a usable CGI-implementation.
Again, gemserv and other servers have usable CGI implementations (including gemserv actually
implementing SCRIPT_NAME and PATH_INFO).
We should call it GGI, btw: Gemini Gateway Interface to distinguish it from CGI.
Why, exactly? I get the fact that you can't name your library CGI.pm, but that doesn't really
warrant changing the name of an entire technology. :P
Just my two cents,
Robert "khuxkm" Miles-- ------------------------------------------------------------------------Frank Jüdes2814 Four Mile RoadCharleston, WV 25312, USACell: +1-713-885-4421-------------------------------------------------------------------------------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210413/b17a2d75/attachment.htm>-------------- next part --------------A non-text attachment was scrubbed...Name: Frank_Juedes.vcfType: text/x-vcardSize: 253 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210413/b17a2d75/attachment.vcf>