- drakma-devel@lists.common-lisp.net - mailman3.common-lisp.net

[drakma-devel] drakma:get-cookies fails to parse cookies with commas in values
by Andrei Stebakov 07 Oct '09

07 Oct '09

One of the web sites started to give me cookies with commas and drakma:get-cookies just crashes on those requests. I distilled my case into a small example like this: (drakma::get-cookies '((:CONTENT-TYPE . "text/html; charset=utf-8") (:LOCATION . "http://www.test") (:SERVER . "Microsoft-IIS/7.0") (:CONTENT-LENGTH . "46") (:DATE . "Sat, 12 Sep 2009 14:58:04 GMT") (:CONNECTION . "close") (:SET-COOKIE . "domain=test.com; expires=Thu, 12-Sep-2109 14:58:04 GMT; session=6,Direct,placeholder,test.com;") (:CACHE-CONTROL . "private")) (puri:parse-uri "http://www.test.com")) It'll throw an exception trying to parse "session=6,Direct,placeholder, test.com" pair and will complain about the commas. I tried to capture the same page with FF Live Http Headers and it has no problems with that. Do you think we could change drakma to be able to digest it as well? Thank you, Andrei

2 5

[drakma-devel] URL-encode and rfc3986
by Red Daly 05 Oct '09

05 Oct '09

Drakma encodes spaces in URLs as pluses instead of "%20"s. It also leaves the characters "$-_.!*'()" unencoded instead of the RFC3986 unencoded set: "-_.~". This is okay for tolerant servers but for other applications it is a bug. For example, in OAuth it is necessary to conform to RFC3986 or the signature will be incorrect for the request. To make Drakma more RFC3986-compliant, replace these four lines in util.lisp: (find char "$-_.!*'()," :test #'char=)) (write-char char out)) ((char= char #\Space) (write-char #\+ out)) with these two: (find char "-_.~" :test #'char=)) (write-char char out)) Best regards, Red

2 1

[drakma-devel] SSL_load_error_strings
by Patrick May 23 Jun '09

23 Jun '09

I'm using drakma to call out to a REST API. It works fine on my laptop under OSX but gives the error: Can't resolve foreign symbol "SSL_load_error_strings" on a CentOS box. OpenSSL is installed. What else do I need to configure? Thanks, Patrick

1 0

[drakma-devel] basic-authorization
by Patrick May 20 Jun '09

20 Jun '09

Are there any known issues with basic-authorization? I'm using the same username and password with drakma:http-request that works with curl's -u argument, but I'm getting a response of "Authorization required." I tried passing the username and password via the url (https://username:password@www.example.com ), but Drakma rejected the format because it expected a port number after the colon. Anyone else run into this? Thanks, Patrick

1 1

[drakma-devel] drakma and personal ssl certificates
by Kevin Raison 14 Apr '09

14 Apr '09

Hello. I am using a site for credit card authorization that requires me to send my personal SSL certificate with any POST. I don't see anything in the Drakma documentation about how to go about this; is it possible? I would rather not use curl, but it does have the -E option that allows for sending certificates to the remote host. Any help would be appreciated! Thanks, Kevin Raison

2 4

[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

[drakma-devel] a bug in send-cookie-p function
by Tomo Matsumoto 25 Feb '09

25 Feb '09

Hello guys, This is my first post here. I think I found a bug in drakma. When I send an http request to the root directory with cookie path set to "/", drakma::send-cookie-p function returns nil. Therefore, drakma don't send any cookie. ex) request-uri: "http://localhost/" or "http://localhost/?key=value" cookie: #<COOKIE sid=xx; expires=Sun, 17-01-2038 19:14:07 GMT; path=/; domain=localhost> That is because the way of using puri's uri functions is wrong. I think Edi expects following code returns "/", but it returns nil. That's why drakma::send-cookie-p function returns nil. (let* ((uri "http://localhost/") (uri (cond ((puri:uri-p uri) (puri:copy-uri uri)) (t (puri:parse-uri uri))))) (puri:uri-path uri)) Do you think it's a bug in drakma? Or has it been already fixed? The versions of related packages. SBCL 1.0.18.debian drakma-0.11.5 puri-1.5.1 I am looking forward to hearing from you. Thanks, Tomo

2 1