From patrick.may at mac.com Thu Jun 18 11:33:21 2009 From: patrick.may at mac.com (Patrick May) Date: Thu, 18 Jun 2009 07:33:21 -0400 Subject: [drakma-devel] basic-authorization Message-ID: <904823E8-237D-4D9B-82EB-F632377D1C3A@mac.com> 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 at www.example.com ), but Drakma rejected the format because it expected a port number after the colon. Anyone else run into this? Thanks, Patrick From patrick.may at mac.com Sat Jun 20 01:24:06 2009 From: patrick.may at mac.com (Patrick May) Date: Fri, 19 Jun 2009 21:24:06 -0400 Subject: [drakma-devel] basic-authorization In-Reply-To: <904823E8-237D-4D9B-82EB-F632377D1C3A@mac.com> References: <904823E8-237D-4D9B-82EB-F632377D1C3A@mac.com> Message-ID: On 18 Jun 2009, at 07:33, Patrick May wrote: > 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 at www.example.com > ), but Drakma rejected the format because it expected a port number > after the colon. I have resolved the problem by fixing my bloody code. That is, the original authorization issue did not lie with drakma. Just as one should not first look for flaws in the compiler or operating system, one cannot reasonably suggest that a bug's root cause lies in a Weitz library. Regards, Patrick From patrick.may at mac.com Tue Jun 23 01:13:30 2009 From: patrick.may at mac.com (Patrick May) Date: Mon, 22 Jun 2009 21:13:30 -0400 Subject: [drakma-devel] SSL_load_error_strings Message-ID: <0F213570-5611-4EBC-9BD5-58E899BDE056@mac.com> 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