spiffy-cgi-handlers feedhttps://bitbucket.org/
List of commits for the spiffy-cgi-handlers repository.en-usBitbucket.org DVCS hostingsupport@bitbucket.org (Bitbucket Support)5Bump version to 0.5
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/5b84ed894f4e
Bump version to 0.5
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/5b84ed894f4e/spiffy-cgi-handlers.release-info">
spiffy-cgi-handlers.release-info
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/5b84ed894f4e/spiffy-cgi-handlers.setup">
spiffy-cgi-handlers.setup
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Thu, 21 Jul 2016 17:34:08 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/5b84ed894f4eAvoid "httpoxy" by omitting HTTP_PROXY conversion.
We don't allow "Proxy" (which doesn't exist as a header) to end
up in the environment as HTTP_PROXY, because it will then influence
many programs such that they will start using the given URL as a
proxy, in effect a MitM-attack on outgoing requests.
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/81467a0eb9d2
Avoid "httpoxy" by omitting HTTP_PROXY conversion.
We don't allow "Proxy" (which doesn't exist as a header) to end
up in the environment as HTTP_PROXY, because it will then influence
many programs such that they will start using the given URL as a
proxy, in effect a MitM-attack on outgoing requests.
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/81467a0eb9d2/cgi-common.scm">
cgi-common.scm
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Thu, 21 Jul 2016 17:30:58 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/81467a0eb9d2Bump version to 0.4
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/5e666d439a03
Bump version to 0.4
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/5e666d439a03/spiffy-cgi-handlers.release-info">
spiffy-cgi-handlers.release-info
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/5e666d439a03/spiffy-cgi-handlers.setup">
spiffy-cgi-handlers.setup
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Sat, 27 Feb 2016 15:02:29 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/5e666d439a03Bump version to 0.4
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/f895123d4f5a
Bump version to 0.4
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/f895123d4f5a/spiffy-cgi-handlers.setup">
spiffy-cgi-handlers.setup
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Sat, 27 Feb 2016 15:01:58 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/f895123d4f5aUse a custom header parser for CGI headers.
The Intarweb header parser has been made more strict according to the
HTTP spec and only allows CRLF as line endings. However, the CGI spec
(only?) allows header lines to end with NL.
Because this is a problem for both cgi and fcgi parsers, this has been
moved into a common "module" which is included from both the cgi and
fcgi handlers. Some common environment setup has also been moved into
this module.
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/930ca7465887
Use a custom header parser for CGI headers.
The Intarweb header parser has been made more strict according to the
HTTP spec and only allows CRLF as line endings. However, the CGI spec
(only?) allows header lines to end with NL.
Because this is a problem for both cgi and fcgi parsers, this has been
moved into a common "module" which is included from both the cgi and
fcgi handlers. Some common environment setup has also been moved into
this module.
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/930ca7465887/cgi-common.scm">
cgi-common.scm
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/930ca7465887/cgi-handler.scm">
cgi-handler.scm
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/930ca7465887/fcgi-handler.scm">
fcgi-handler.scm
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Sat, 27 Feb 2016 14:57:11 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/930ca7465887Fix compiler warning which would be a runtime error
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/4382f28785cc
Fix compiler warning which would be a runtime error
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/4382f28785cc/fcgi-handler.scm">
fcgi-handler.scm
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Sat, 27 Feb 2016 12:04:37 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/4382f28785ccRemove single quote in #error message.
This gets rid of a compiler warning
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/8d98ddc804ed
Remove single quote in #error message.
This gets rid of a compiler warning
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/8d98ddc804ed/fork-exec.c">
fork-exec.c
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Sat, 27 Feb 2016 12:04:37 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/8d98ddc804edRemove dependency on regex egg by using irregex.
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/09af414e0952
Remove dependency on regex egg by using irregex.
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/09af414e0952/cgi-handler.scm">
cgi-handler.scm
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/09af414e0952/fcgi-handler.scm">
fcgi-handler.scm
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/09af414e0952/spiffy-cgi-handlers.meta">
spiffy-cgi-handlers.meta
</a>
</li>
</ul>
noreply@bitbucket.org (Peter Bex)Sat, 27 Feb 2016 12:04:05 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/09af414e0952Version metadata wrangling for egg release.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/4de1a964810d
Version metadata wrangling for egg release.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/4de1a964810d/spiffy-cgi-handlers.release-info">
spiffy-cgi-handlers.release-info
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/4de1a964810d/spiffy-cgi-handlers.setup">
spiffy-cgi-handlers.setup
</a>
</li>
</ul>
Mon, 13 Oct 2014 22:39:23 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/4de1a964810dRework the FCGI header parsing to fix spurious line break issues
We need to sanitize and filter the FCGI headers that come back from the
FCGI process in order to turn them into HTTP headers.
The code that did this was naive and ended up stripping line breaks from
the first part of the non-header response and adding an extra line break
into responses that were large enough to require more than a single
read from the pipe connecting the CHICKEN process with the FCGI process.
Here we rewrite the offending pieces to slurp the data into a buffer and
search it for the '\r\n\r\n' token that denotes the end of the headers
instead of trying to split the data on a line break and then reconstitute
it afterwards.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/6951353097a0
Rework the FCGI header parsing to fix spurious line break issues
We need to sanitize and filter the FCGI headers that come back from the
FCGI process in order to turn them into HTTP headers.
The code that did this was naive and ended up stripping line breaks from
the first part of the non-header response and adding an extra line break
into responses that were large enough to require more than a single
read from the pipe connecting the CHICKEN process with the FCGI process.
Here we rewrite the offending pieces to slurp the data into a buffer and
search it for the '\r\n\r\n' token that denotes the end of the headers
instead of trying to split the data on a line break and then reconstitute
it afterwards.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/6951353097a0/fcgi-handler.scm">
fcgi-handler.scm
</a>
</li>
</ul>
Mon, 13 Oct 2014 22:39:17 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/6951353097a0Version metadata wrangling for egg release.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/d0d9d8878cd2
Version metadata wrangling for egg release.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/d0d9d8878cd2/spiffy-cgi-handlers.release-info">
spiffy-cgi-handlers.release-info
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/d0d9d8878cd2/spiffy-cgi-handlers.setup">
spiffy-cgi-handlers.setup
</a>
</li>
</ul>
Sun, 04 May 2014 17:57:08 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/d0d9d8878cd2Ensure the FastCGI process always receives a blocking socket
From version 0.2.3, the socket egg immediately places the sockets it
creates into non-blocking mode. In previous versions it only used to do
this during socket-connect and socket-accept. As these procedures were
never called on the socket we create for the FastCGI process we always has
a regular blocking socket in hand.
The FCGX_Accept_r() call expects a blocking socket. If the socket does not
block then FCGX_Accept_r() returns a non-zero value and the FastCGI process
exits.
Here we ensure that the socket is in blocking mode after we fork but before
we exec the FastCGI binary. This means that the child process gets the
blocking socket that it expects but the socket in the CHICKEN parent is as
the socket egg created it.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/826d47287d3c
Ensure the FastCGI process always receives a blocking socket
From version 0.2.3, the socket egg immediately places the sockets it
creates into non-blocking mode. In previous versions it only used to do
this during socket-connect and socket-accept. As these procedures were
never called on the socket we create for the FastCGI process we always has
a regular blocking socket in hand.
The FCGX_Accept_r() call expects a blocking socket. If the socket does not
block then FCGX_Accept_r() returns a non-zero value and the FastCGI process
exits.
Here we ensure that the socket is in blocking mode after we fork but before
we exec the FastCGI binary. This means that the child process gets the
blocking socket that it expects but the socket in the CHICKEN parent is as
the socket egg created it.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/826d47287d3c/fork-exec.c">
fork-exec.c
</a>
</li>
</ul>
Sun, 04 May 2014 16:52:16 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/826d47287d3cInclude the query string, as well as the path, in REQUEST_URI
...also use 'req' rather than '(current-request)'.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/e6a3535ea79c
Include the query string, as well as the path, in REQUEST_URI
...also use 'req' rather than '(current-request)'.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/e6a3535ea79c/fcgi-handler.scm">
fcgi-handler.scm
</a>
</li>
</ul>
Tue, 28 Jan 2014 14:43:35 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/e6a3535ea79cA Chicken Scheme egg release-info file
...as specified at
http://wiki.call-cc.org/releasing-your-egg
Signed-off-by: Andy Bennett <andyjpb@knodium.com
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/ad963fed4efd
A Chicken Scheme egg release-info file
...as specified at
http://wiki.call-cc.org/releasing-your-egg
Signed-off-by: Andy Bennett <andyjpb@knodium.com
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/ad963fed4efd/spiffy-cgi-handlers.release-info">
spiffy-cgi-handlers.release-info
</a>
</li>
</ul>
Sun, 04 Nov 2012 22:40:52 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/ad963fed4efdcgi-handler and fcgi-handler eggs to accompany spiffy
CGI and FastCGI handlers for a small but powerful web server.
cgi-handler has been factored out of spiffy.
Proposals to add fcgi-handler to spiffy resulted in the decision to
maintain these handlers in a dedicated egg.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/3bb6c1e18797
cgi-handler and fcgi-handler eggs to accompany spiffy
CGI and FastCGI handlers for a small but powerful web server.
cgi-handler has been factored out of spiffy.
Proposals to add fcgi-handler to spiffy resulted in the decision to
maintain these handlers in a dedicated egg.
Signed-off-by: Andy Bennett <andyjpb@knodium.com>
<ul>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/LICENSE.TERMS.fcgi">
LICENSE.TERMS.fcgi
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/cgi-handler.scm">
cgi-handler.scm
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/fastcgi.h">
fastcgi.h
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/fcgi-handler.scm">
fcgi-handler.scm
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/fork-exec.c">
fork-exec.c
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/fork-exec.h">
fork-exec.h
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/spiffy-cgi-handlers.meta">
spiffy-cgi-handlers.meta
</a>
</li>
<li>
<a href="https://bitbucket.org/knodium/spiffy-cgi-handlers/src/3bb6c1e18797/spiffy-cgi-handlers.setup">
spiffy-cgi-handlers.setup
</a>
</li>
</ul>
Sun, 04 Nov 2012 22:39:42 +0000https://bitbucket.org/knodium/spiffy-cgi-handlers/commits/3bb6c1e18797