Closed jtbx closed 3 days ago
That's actually kinda expected, fastcgi needs to be run through a special helper thing, otherwise it isn't set up right and has a null pointer when you run it (though you can still test it by running like ./test GET /
).
From the docs:
FastCGI is managed from an outside helper, there's one built into Microsoft IIS, Apache httpd, and Lighttpd, and a generic program you can use with nginx called spawn-fcgi.
This is because fastcgi processes are spun up and down on demand so there's some extra meta management stuff in there that is externally fed into it.
What web server are you using?
You can also run it like ./test --port 4432
to listen on a particular port for the web server to connect to your fastcgi instance.
That's actually kinda expected, fastcgi needs to be run through a special helper thing, otherwise it isn't set up right and has a null pointer when you run it (though you can still test it by running like
./test GET /
).
Ah I was trying to set it up similar to a reverse proxy, with the fastcgi process running in the background constantly. Makes sense
From the docs:
FastCGI is managed from an outside helper, there's one built into Microsoft IIS, Apache httpd, and Lighttpd, and a generic program you can use with nginx called spawn-fcgi.
This is because fastcgi processes are spun up and down on demand so there's some extra meta management stuff in there that is externally fed into it.
What web server are you using?
I'm trying to set it up with nginx, I think I've got it going now. Thanks for clearing that up.
nginx has built in support for scgi reverse proxy too which you might prefer, you can easily start and stop the server there yourself as well.
Hi Adam, cgi.d segfaults when compiled with
-version=fastcgi
:Here is a gdb backtrace:
The code used is the first example in the cgi.d documentation. Do you know what is happening here?