From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=NORMAL_HTTP_TO_IP,
	NUMERIC_HTTP_ADDR autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 11264 invoked from network); 24 Apr 2022 21:09:31 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 24 Apr 2022 21:09:31 -0000
Received: from maat.thinktankworkspaces.com ([45.79.94.76]) by 9front; Sun Apr 24 17:08:21 -0400 2022
Message-ID: <E3B949ADEF5E9F77DD687479A35ABE7D@thinktankworkspaces.com>
To: 9front@9front.org
Date: Sun, 24 Apr 2022 14:08:19 -0700
From: william@thinktankworkspaces.com
In-Reply-To: <9CF54D7023B5262B0618877CACE7FDB2@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: rich-client-scale core-based controller 
Subject: Re: [9front] https exec header invalid
Reply-To: 9front@9front.org
Precedence: bulk

daunting... When I run it command line it get the following. 

tlssrv -D -c /sys/lib/tls/think.pem -l /tmp/log/https /cfg/maat/service.www/tcp80 $*

maat Apr 24 13:48:43  tls reports tlsServer2
maat Apr 24 13:48:43  tls reports initial msgRecv failed
maat Apr 24 13:48:43  tls reports failed: tls hungup
https://45.79.94.76


cat tcp80
#!/bin/rc
exec /rc/bin/rc-httpd/rc-httpd >>[2]/sys/log/www

was not sure if I needed to change something in select handler

if(~ $SERVER_NAME 45.79.94.76){
	PATH_INFO=$location
	FS_ROOT=/usr/www/werc/sites/$SERVER_NAME
	exec static-or-cgi /usr/www/werc/bin/werc.rc
}

like a redirect or something?

Quoth ori@eigenstate.org:
> Quoth william@thinktankworkspaces.com:
> > 
> > Why am I getting: exec header invalid. not much more in the logs and nothing in /sys/log/http
> > 
> > I will rebuild the key and pem for security but I think I'm missing
> > something. Here is my configuration steps. 
> 
> that error has nothing to do with the https config,
> and everything to do with a binary that you're running
> being invalid.
> 
>