From owner-freebsd-questions Wed Jul 17 12:30:21 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA11945 for questions-outgoing; Wed, 17 Jul 1996 12:30:21 -0700 (PDT) Received: from fiber.net (cpayne@optical.fiber.net [204.250.13.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA11940 for ; Wed, 17 Jul 1996 12:30:16 -0700 (PDT) Received: by fiber.net (NX5.67f2/NX3.0M) id AA09097; Wed, 17 Jul 96 13:34:34 -0600 Message-Id: <9607171934.AA09097@fiber.net> X-Fibernet-Tip: Don't quote more than you contribute! Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Carl Payne Date: Wed, 17 Jul 96 13:34:31 -0600 To: freebsd-questions@freebsd.org Subject: CGI executes only on http, not https Reply-To: cpayne@fiber.net Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ...And, once again, I prove how subject lines are not my forte... We have a VDN client whose CGI scripts execute just fine when accessed NON-SSL, but when addressed through their https URL you get: File Not Found The requested URL /cgi-bin/file.cgi was not found on this server OK, looks elementary enough. Here's what I've done: Made sure there was a "Directory cgi-bin / allow from all" type of block in the ssl_conf/httpd.conf same as the non-SSL VDN conf file... Made sure the srm.conf in ssl_conf supported .cgi as a file extension; this also appears in the httpd.conf Tried to make sure everything that allowed cgi execution from the non-SSL VDN was also in the ssl_conf/httpd.conf Checked both the documentation (sic) and my favorite search engine. Haven't seen the archive, nor a 3rd party FAQ yet. Right now, I'm approaching Wit's End (the last stop before Dead Man's Curve), and I'm wondering what would keep a CGI script invisible to the SSL VDN but available to the non-SSL one. All help appreciated; thanks in advance. Carl