9front - general discussion about 9front
 help / color / mirror / Atom feed
From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] https exec header invalid
Date: Sun, 24 Apr 2022 14:08:19 -0700	[thread overview]
Message-ID: <E3B949ADEF5E9F77DD687479A35ABE7D@thinktankworkspaces.com> (raw)
In-Reply-To: <9CF54D7023B5262B0618877CACE7FDB2@eigenstate.org>

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.
> 
> 



  reply	other threads:[~2022-04-24 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23 23:08 william
2022-04-24  1:37 ` ori
2022-04-24 21:08   ` william [this message]
2022-04-26 23:00     ` ori

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=E3B949ADEF5E9F77DD687479A35ABE7D@thinktankworkspaces.com \
    --to=william@thinktankworkspaces.com \
    --cc=9front@9front.org \
    --subject='Re: [9front] https exec header invalid' \
    /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

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 NNTP newsgroup(s).