From: Andy Romens <romens.andy@hotmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Lighttpd and Perl
Date: Thu, 30 Sep 2021 10:07:24 +0000 [thread overview]
Message-ID: <CH0PR14MB493056E9F7B26A4F7DBA6FC0FBAA9@CH0PR14MB4930.namprd14.prod.outlook.com> (raw)
Good morning all,
I am running into a bit of what appears a noob issue with lighttpd.
Short and sweet version is I am transitioning from Apache to lighttpd.
Gotten pretty far, except now I am having issues with parsing.
Our website will run a command in a browser like ‘server/cgi-bin/myscript.pl?prod,eventhist’ in the web browser. With Apache, it will split everything after the ‘?’ As variables, and return a nicely formatted html result page.
However, after switching to lighttpd, it’s not passing those variables anymore. When I run the script in Cygwin, it works just fine.
I’ve been banging my head on this problem for a few days now, so any assistance would be greatly appreciated.
Thanks,
-Andy
next reply other threads:[~2021-09-30 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 10:07 Andy Romens [this message]
2021-09-30 21:28 ` gs-cygwin.com
2021-10-01 0:48 ` Brian Inglis
2021-10-06 23:56 ` Andy Romens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CH0PR14MB493056E9F7B26A4F7DBA6FC0FBAA9@CH0PR14MB4930.namprd14.prod.outlook.com \
--to=romens.andy@hotmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).