Experimental IRC log happs-2008-08-04

Available formats: content-negotiated html turtle (see SIOC for the vocabulary)

Back to channel and daily index: content-negotiated html turtle

These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.

08:13:57<vitaliy_akimov>hi
08:14:10<vitaliy_akimov>can i run CGI application on HAppS?
09:47:23<MarcWeber>vitaliy_akimov: Of course you can. But I'm not sure wether the CGI interface is already implemented.. I could'nt find any function / file named *cgi*
09:56:43<hansfbaier>installation of happs fails for me: After a while it hangs here: http://hpaste.org/9376 (This is so frustrating.....)
09:56:50<hansfbaier>any suggestions?
09:56:56<eelco>vitaliy_akimov: yes, look at simpleHTTP' from SimpleHTTP (notice the prime)
09:58:23<eelco>hansfbaier: cabal install hslogger
09:59:40<hansfbaier>eelco: shouldnt sp do that for me?
10:00:14<eelco>sp's default 'map' doesn't know about hslogger
10:00:45<eelco>you could teach it that, but using cabal is easier
10:42:28<hansfbaier>Thanks, folks!
10:49:38<vitaliy_akimov>eelco: i've just seen simpleHTTP', and i haven't noticed anything connected with CGI
10:50:01<vitaliy_akimov>eelco: maybe i have wrong version? i have 0.9.2.2
23:18:17<dcoutts>chr1s : any idea what http error code one is supposed to return if a POST or PUT is being rejected for application layer reasons?
23:18:35<dcoutts>ie we validate it and decide it's not valid
23:23:38<stepcut`>http://thoughtpad.net/alan-dean/http-headers-status.gif
23:23:47<dcoutts>ok, seems 400 is the generic catch all here for application layer rejections
23:23:48<stepcut`>400 bad request, perhaps?
23:23:57<dcoutts>stepcut`: yeah, seems so
23:24:04<dcoutts>it's not that clear in the http spec
23:24:13<stepcut`>412 perhaps ?
23:24:30<dcoutts>it reads as if it's purely for protocol layer errors
23:24:59<stepcut`>no, probably not 412
23:25:01<dcoutts>Precondition Failed
23:25:01<dcoutts>The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource metainformation (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
23:25:08<dcoutts>right not 412
23:25:14<stepcut`>I misread the chart at first
23:27:32<dcoutts>that diagram doesn't make it very clear either, for validating input
23:27:48<dcoutts>well, it's not just valid input, it's if it conforms to some app layer policy
23:27:58<dcoutts>not just well-formed I mean
23:28:26<dcoutts>that diagram puts it very early as a "malformed" test
23:39:33<stepcut>yeah, though by process of elimination, it seems like the only choice
23:42:18<dcoutts>aye

Back to channel and daily index: content-negotiated html turtle