It was thus said that the Great Omar Polo once stated: > > Sean Conner <sean at conman.org> writes: > > > [...] > > > > You don't split the query. You pass it in, as is, from the request, in > > QUERY_STRING. Play around with: > > > > gemini://gemini.conman.org/cgi > > > > It will show all the variables, command line arguments and a breakdown of > > the query string. > > Thanks for providing that page. I played a bit with it while fixing my > CGI implementation and now I believe gmid behaves just like GLV-1.12556 > does (minus the argument list). I have to do some changes in order to > access the raw query string when I'm about to execute the CGI script. > > One thing that your page doesn't show are the TLS-related environment > variables. I remember you wrote about them in a previous message on > this list. Ah. To see those, use a client certificate and go here: gemini://gemini.conman.org/private/cgi-sample > I built a similar page, hosted at > > gemini://gemini.omarpolo.com/cgi/env Cool. But you only set AUTH_TYPE and REMOTE_USER if a client certificate is present, otherwise, they're not set. Same for the TLS_* variables. Also, PWD, LANG and LC_COLLATE aren't required (they're not part of the CGI spec). I included LANG to ensure proper charset usage of any program executed, LC_COLLATE just because and PATH (not PWD) in case I need to execute a Unix command from a CGI script. > Thanks You're welcome. -spc
---
Previous in thread (6 of 7): 🗣️ Omar Polo (op (a) omarpolo.com)