accessing https URLS with basic authentification

[Bernard Devlin]

Basic Auth should still work with https.

I think the problem might be to do with the verification of the SSL
certificate.  Try running this before you make your https URL call:

libUrlSetSSLVerification false

The only thing that gives me pause in suggesting this as the cause, is
that I would expect curl to also fail if there was a problem with the
SSL certificate (i.e. the certification chain is broken).   Then
again, maybe it is that curl has a chain of certs that will verify the
cert of the site you are trying to connect with.  (I thought for some
years now curl was not supplied with its own certs).

Bernard


On Fri, May 8, 2009 at 12:43 AM, Ben Rubinstein <benr_mc at cogapp.com> wrote:
> I can load an "https" URL fine.
>
> I can load an "http" URL protected using 'basic' authentification, using
> either the "http://user:password@www.somewhere.com/" format, or by using the
> HTTPHeaders property to explicitly add an "Authorization: Basic xxx" header.
>
> But I can't load an "https" URL that's protected using basic
> authentification, using either of the methods described above.
>
> Is this a known problem?  Can anyone else either reproduce this problem, or
> alternatively confirm that they _can_ load such a URL?
>
> (NB1 this is on Mac OS X, Rev 3.0 and 3.5.)
>
> (NB2 I can retrieve the URL fine using "curl" in the terminal - and in fact
> for now I'm working around the problem by using shell() to invoke curl.  But
> I really want to handle URLs of this form in the same way I'm handling other
> http URLs in my app, which give me more control.)
>
> Any insights gratefully received,
>
> TIA
>
> Ben
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>