[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] fixnum problem in http egg is back, magically.
From: |
Robin Lee Powell |
Subject: |
Re: [Chicken-users] fixnum problem in http egg is back, magically. |
Date: |
Sat, 15 Mar 2008 19:23:33 -0700 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
On Sat, Mar 15, 2008 at 07:10:14PM -0700, Robin Lee Powell wrote:
> [SPIFFY: (root) reading /home/rlpowell/svn/sert/test.scm with size
> 222.0#<unspecified>]
> Error: (file-read) bad argument type - not a fixnum: 222.0
> Error: 500 Internal server error
*Huh*.
I've managed to track the problem down. It occurs when spiffy tries
to serve a file whose extension it doesn't know. For testing
purposes, I have:
(spiffy-file-ext-handlers `(
("wu" ,web-unity-handler)
("wu2" ,(web-unity-handler
"/home/rlpowell/svn/sert/spiffy-dispatcher.scm"))
("ws" . ,web-scheme-handler)
))
If I make "test.html" and try to access it, I get:
[waiting for requests...#<unspecified>]
[request 0 from 64.81.66.169; thread3 (of 1) started...#<unspecified>]
[read: "GET /test.html HTTP/1.1"#<unspecified>]
[request: method=GET, url=/test.html, protocol=HTTP/1.1#<unspecified>]
[attributes: (("accept" . "*/*") ("host" . "chain.teddyb.org:7623")
("user-agent" . "curl/7.17.1 (x86_64-pc-linux-gnu) libcurl/7.17.1
OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.1 libssh2/0.18"))#<unspecified>]
[handling GET request...#<unspecified>]
[raw request value: #<http:request>#<unspecified>]
[request handling: args = () resource = #f#<unspecified>]
[SPIFFY: set-header: "Content-Type" -> "text/html"#<unspecified>]
[SPIFFY: set-header: "Content-Length" -> "4"#<unspecified>]
[Response: HTTP/1.1 200 OK#<unspecified>]
[SPIFFY: (root) reading /home/rlpowell/svn/sert/test.html with size
4.0#<unspecified>]
Error: (file-read) bad argument type - not a fixnum: 4.0
Error: 500 Internal server error
[SPIFFY: set-header: "Content-Length" -> "556"#<unspecified>]
[Response: HTTP/1.1 500 Internal server error#<unspecified>]
[thread3 (of 1) kept alive, reading next request...#<unspecified>]
[client closed connection or read timed out.#<unspecified>]
[closing connection...#<unspecified>]
[thread3 finished.#<unspecified>]
I really don't see how this makes any sense, but I'm hoping that'll
be enough for someone who knows the code to at least make the error
more useful.
-Robin
--
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/