Hi
I am getting this (Got Content-Length header although input chunking is on.") syntax-error when I do some api calls to twitter and facebook.
The drakma code says to
;; see RFC 2616, section 4.4
But if I look at the documentation 4.4 says
"If a message is received with both a Transfer-Encoding header field and a
Content-Length header field, the latter MUST be ignored."
I have hacked my local copy of drakma to do just that and it seems to work."
Am I maybe missing something or not reading the spec right?
Regards
Phil
Hi
Using Drakma-1.3.2 (via quicklisp) and Sbcl-1.1.9 on Linux (Debian Wheezy):
I believe it is allowed to send parameters with a PUT request, just as with a POST request, but Drakma only allows POST with parameters.
In request.lisp, changing this
(when (and file-parameters-p (not (eq method :post)))
(parameter-error "Don't know how to handle parameters in ~S, as this is not a POST request."
To this
(when (and file-parameters-p (not (member method '(:post :put))))
(parameter-error "Don't know how to handle parameters in ~S, as this is not a POST or PUT request."
Allows PUT parameters.
I need this change for drakma to work with an common lisp interface to the paymill payment service api: https://www.paymill.com/
I would like to release the the paymill-api, but if Drakma won't let me use parameters in a put request, I will have to ship a forked version of it with the api.
Regards
Peter
(ps. Just to be clear: I'm not talking about form-data - that IS only allowed with POST.)
Hi,
I'm trying to use drakma with clisp on windows and I get an error when I
use the :stream argument on http-request:
NO-APPLICABLE-METHOD: When calling #1=#<STANDARD-GENERIC-FUNCTION
#2=(SETF FLEXI-STREAMS:FLEXI-STREAM-ELEMENT-TYPE)> with arguments
#3=(CHARACTER
T), no method is applicable.
[Condition of type CLOS:METHOD-CALL-TYPE-ERROR]
As a second issue, the link to this email list on
http://weitz.de/drakma/ is a 404.
Hi
I am getting this syntax-error when I do some api calls to twitter and
facebook.
The drakma code says to
;; see RFC 2616, section 4.4
But if I look at the documentation 4.4 says
"If a message is received with both a Transfer-Encoding header field and
a Content-Length header field, the latter MUST be ignored."
I have hacked my local copy of drakma to do just that and it seems to work."
Am I maybe missing something or not reading the spec right?
Regards
Phil
I ran across an SSL website that requires TLSv1. `drakma:http-request'
does not allow passing an SSL method to 'cl+ssl:make-ssl-client-stream'
(via `drakma:make-ssl-stream'). It would be nice if it did.
Carlos Konstanski
Sr. Systems Administrator
T 208.578.3733
C 208.720.7511
ckonstanski(a)marketron.com<mailto:ckonstanski@marketron.com>
[www.marketron.com]<https://www1.gotomeeting.com/register/644819568>
The information contained in this e-mail message may be confidential and
protected from disclosure. If you are not the intended recipient, any
dissemination, distribution or copying is strictly prohibited. If you
think that you have received this e-mail message in error, please notify
the sender immediately by replying to this message and then delete it
from your system.
I have a list of IP addresses to poll and want to catch the USOCKET:TIMEOUT-ERROR from Drakma when a machine isn't available, log a message, and continue on mapping over the list. Does anyone have an example of how to do this?
Thanks,
Patrick