I'm experimenting with the althttpd.c web server. As a simple first test I
created a static html file and a lua script file. The static file displays
as expected in firefox. The lua file, which simply reads in the same
static html file and writes it back to stdout ends up being truncated and
> -SNIP-
>
> You do actually have to have the name of the CGI script in there.
> Otherwise, althttpd has know way of knowing what script to run.
>
Thanks for the explanations, comprehend all.
> >
> > Test #5:
> > Browser URL: http://127.0.0.1:8080/home/index.cgi/some/extra/path/info/
> >
> Fixed.
Thanks!
> Now with two users, maybe it is time to separate the
> althttpd.c code and documentation out into a separate repository
> (rather than commingling it with the SQLite documentation), get a
> domain name, and set up a website just for althttpd.c :-)
Sounds good to me, though
Hello,
Should "index.cgi" from line number 1923 in subject check in include a
leading forward slash? My index.cgi scripts aren't being found with
this version (or any subsequent version) unless I explicitly include
it as part of the request uri. I added the slash and recompiled and
it started
Without commenting on the security (or lack thereof) of any of the
settings below, here are the systemd unit files I'm using on Centos.
As the documentation only provides an example for Xinetd I thought I'd
submit these for possible inclusion:
[root@www sodface]# cat
Dr. Hipp,
I'm using althttpd to serve files from a personal Linux package
repository. There are 38 instances of package names which contain at
least one plus sign, currently one of the characters substituted with
an underscore by althttpd. This results in a 404 file not found error
and makes
6 matches
Mail list logo
