March 2009 - drakma-devel@common-lisp.net

[drakma-devel] error while using ssl connections in new drakma
by Andrei Stebakov 13 Mar '09

13 Mar '09

When calling: (http-request "https://www.fortify.net/cgi/ssl_2.pl") I have Unhandled memory fault at #x14. [Condition of type SB-SYS:MEMORY-FAULT-ERROR] Restarts: 0: [RETRY] Retry SLIME interactive evaluation request. 1: [ABORT] Return to SLIME's top level. 2: [ABORT] Exit debugger, returning to top level. Backtrace: 0: (SB-SYS:MEMORY-FAULT-ERROR) 1: (SB-SYS:MEMORY-FAULT-ERROR)[:EXTERNAL] 2: ("foreign function: #x806452C") 3: ("foreign function: #x8064860") 4: ("foreign function: #xB77B6A10") 5: ("foreign function: #xB77B6CE8") 6: (CL+SSL::SSL-SET-FD #<unavailable lambda list>) 7: (CL+SSL::INSTALL-HANDLE-AND-BIO #<unavailable lambda list>) 8: (CL+SSL:MAKE-SSL-CLIENT-STREAM #<unavailable lambda list>)[:EXTERNAL] 9: (HTTP-REQUEST "https://www.fortify.net/cgi/ssl_2.pl")[:EXTERNAL] I use sbcl-1.0.23 on Ubuntu 32 bit. cffi_0.10.4 drakma-1.0.0 latest cl+ssl from cvs What am I missing? Thank you, Andrei

3 3

Re: [drakma-devel] [hunchentoot-devel] "Proxy Error" with new Hunchentoot
by Edi Weitz 08 Mar '09

08 Mar '09

On Sat, Mar 7, 2009 at 11:55 PM, Andrei Stebakov <lispercat(a)gmail.com> wrote: > After I upgraded to new chunga things started to move, but now I have > a problem with drakma:http-request. It returns a binary array on a > request like (http-request "http://lisp.org/"), so all my functions > depending on http-request fail. I'll ask about it in drakma ml. As I said in the release announcements, the new and the old (with 1.x.x being the dividing line) versions of Drakma, Hunchentoot, and Chunga are mutually incompatible. If you upgrade one of them, you need to upgrade all three libraries. HTH, Edi.

1 0

[drakma-devel] http-request returns a binary array...
by Andrei Stebakov 08 Mar '09

08 Mar '09

I wonder what am I missing when a call like (http-request "http://lisp.org/") returns a binary array: #(60 116 105 116 108 101 62 114 101 100 105 114 101 99 116 46 46 46 60 47 116 105 116 108 101 62 60 109 101 116 97 32 104 116 116 112 45 101 113 117 105 118 61 34 82 101 102 114 101 115 104 34 32 99 111 110 116 101 110 116 61 34 48 59 32 117 114 108 61 47 97 108 117 47 104 111 109 101 34 62) 200 ((:DATE . "Sat, 07 Mar 2009 22:56:52 GMT") (:CONNECTION . "Close") (:SERVER . "AllegroServe/1.2.50") (:TRANSFER-ENCODING . "chunked")) #<PURI:URI http://lisp.org> #<FLEXI-IO-STREAM {107E2C79}> T " OK" Before I upgraded to the new hunchentoot and drakma and chunga it would give me a text string. Thank you, Andrei

2 3

[drakma-devel] Conditional (#+/#-) expressions in DRAKMA
by Joshua TAYLOR 04 Mar '09

04 Mar '09

Hello, With the new release of DRAKMA I was looking over some of the source, and came across code like (some-function ...#+:clisp #+:clisp :clisp-arg clisp-val) which I'd never seen before. I started to investigate, and a discussion even started on c.l.l [1]. It turns out that not all Lisps treat these constructions in the same way. Particularly, in the case of #-feature #-feature, some process the second #-feature with *READ-SUPPRESS* bound to T, so the behavior is like #-CL:NIL. At any rate, it seems a bit safer and more portable not to nest the conditionalized expressions. The only place I found these was in request.lisp, and even there only in three places. I've attached a diff in which they are changed to the safer form. I've also added leading colons to openmcl, since the rest of the source seemed to use that style. Thanks for a great HTTP client—DRAKMA's the one I turn to when I need a Lisp HTTP client. //JT [1] http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/8d50284a… -- ===================== Joshua Taylor tayloj(a)cs.rpi.edu, jtaylor(a)alum.rpi.edu "A lot of good things went down one time, back in the goodle days." John Hartford

2 3