On 8/23/13 4:23 PM, Trevor DeVore wrote:
On Fri, Aug 23, 2013 at 1:21 PM, J. Landman Gay wrote:
On 8/23/13 5:14 AM, Dave Cragg wrote:
I know that https connections through a proxy were not supported in
the past. I'm assuming that is still the case.
Can anyone verify this? If it's true, I'm
On Fri, Aug 23, 2013 at 1:21 PM, J. Landman Gay wrote:
> On 8/23/13 5:14 AM, Dave Cragg wrote:
>
>> I know that https connections through a proxy were not supported in
>> the past. I'm assuming that is still the case.
>>
>
> Can anyone verify this? If it's true, I'm in trouble.
This is still tru
On 8/23/13 5:14 AM, Dave Cragg wrote:
I know that https connections through a proxy were not supported in
the past. I'm assuming that is still the case.
Can anyone verify this? If it's true, I'm in trouble.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
On 23 Aug 2013, at 07:59, FlexibleLearning.com
wrote:
> I just tried "put the libURLSetSSLVerification" on Windows and got a compile
> error.
>
> Without a dictionary entry, however, I am only guessing that it would return
> True/False.
Hugh,
libURLSetSSLVerification is a message handler (co
I just tried "put the libURLSetSSLVerification" on Windows and got a compile
error.
Without a dictionary entry, however, I am only guessing that it would return
True/False.
Meanwhile, access to data supplied by an https url seems unavailable when
using Mac OS X.
Bugger.
Hugh Senior
FLCo
On 8
On 8/22/13 11:42 PM, J. Landman Gay wrote:
Thierry Douez wrote:
If I remember well, you were setting libUrlSetSSLVerification to
false ?
Still true?
Actually I haven't set it to true yet,
Er, I mean, haven't set it to false yet. So far I haven't set
libURLSSLVerification at all y
Thierry Douez wrote:
>
>If I remember well, you were setting
>libUrlSetSSLVerification to false
>?
>
>
>Still true?
Actually I haven't set it to true yet, but after seeing the problem come up
twice now I'm thinking maybe I should do the https check that Neil suggested
when the app starts
Hi Jacque,
It sounds like the issue only occurs on OS X 10.6, right? Mac 10.7+ and
Windows machines are not affected? Do you know?
>>>
>>>
>>> Umm, it's not working on Mac 10.7.5 right now on my box.
>>>
>>
>> And it's not working on Mac 10.8.4 on mine.
>>
>> Meanwhile the entire item
On 8/22/13 12:21 PM, Ben Rubinstein wrote:
And libUrlSetSSLVerification, mentioned (I think) in Thierry's response
from RunRev support, does not appear in any documentation that I can find.
I just found it in the SSLCertificates entry in the dictionary. The info
should probably also be cross-
On 8/22/13 12:21 PM, Ben Rubinstein wrote:
On 24/06/2013 16:28, Thierry Douez wrote:
2013/6/24 J. Landman Gay
It sounds like the issue only occurs on OS X 10.6, right? Mac 10.7+ and
Windows machines are not affected? Do you know?
Umm, it's not working on Mac 10.7.5 right now on my box.
On 24/06/2013 16:28, Thierry Douez wrote:
2013/6/24 J. Landman Gay
It sounds like the issue only occurs on OS X 10.6, right? Mac 10.7+ and
Windows machines are not affected? Do you know?
Umm, it's not working on Mac 10.7.5 right now on my box.
And it's not working on Mac 10.8.4 on mine.
Thanks Mark, that's exactly what I needed to know. This stuff is out of
my league.
On 6/24/13 11:03 AM, Mark Wilcox wrote:
Another suggestion would be setting the property
libUrlSetSSLVerification to false as this may also resolve the
issue..
Another question: does setting libUrlSetSSLVer
Thanks Mark.
In the meantime, I found this one for more security:
http://forums.runrev.com/viewtopic.php?f=11&t=6995&p=31804&hilit=https#p31804
Regards,
Thierry
2013/6/24 Mark Wilcox
>
>
> >> Another suggestion would be setting the property
> libUrlSetSSLVerification
> >> to false
> >> as t
>> Another suggestion would be setting the property libUrlSetSSLVerification
>> to false
>> as this may also resolve the issue..
> Another question: does setting libUrlSetSSLVerification to false mean
> security is turned off completely, or only that the certificate isn't checked?
Not doing SS
2013/6/24 J. Landman Gay
>
> Another suggestion would be setting the property libUrlSetSSLVerification
>> to false
>> as this may also resolve the issue..
>>
>
> Another question: does setting libUrlSetSSLVerification to false mean
> security is turned off completely, or only that the certificat
Hello Jacque,
2013/6/24 J. Landman Gay
Thanks for posting that, Thierry. I'm working on a project that needs SSL
> and your problem had me worried.
>
Well, it still worries me :(
>
> It sounds like the issue only occurs on OS X 10.6, right? Mac 10.7+ and
> Windows machines are not affe
Another suggestion would be setting the property libUrlSetSSLVerification
to false
as this may also resolve the issue..
Another question: does setting libUrlSetSSLVerification to false mean
security is turned off completely, or only that the certificate isn't
checked?
--
Jacqueline Landman
Thanks for posting that, Thierry. I'm working on a project that needs
SSL and your problem had me worried.
It sounds like the issue only occurs on OS X 10.6, right? Mac 10.7+ and
Windows machines are not affected? Do you know?
On 6/24/13 9:07 AM, Thierry Douez wrote:
2013/6/22 Thierry Douez
2013/6/22 Thierry Douez
> Coming back :(
>
> More details:
>
> I'm on MacOS.
>
> Restarting my Mac and my Internet Box and got again the same error:
>
> post myData to url "https://myDomain";
>
>
>
> But, executing this line of script always works:
>
> get shell("curl -s -d" && quote & myData
Coming back :(
More details:
I'm on MacOS.
Restarting my Mac and my Internet Box and got again the same error:
post myData to url "https://myDomain";
But, executing this line of script always works:
get shell("curl -s -d" && quote & myData & quote && "https://myDomain";)
Executing the sa
Merci Pierre,
looks like option 2 was the culprit.. everything works well again :)
Thierry Douez - http://sunny-tdz.com
Maker of sunnYperl - sunnYmidi - sunnYmage
2013/6/18 Pierre Sahores
> Hi,
>
> Would say that two events may be responsible o
Hi,
Would say that two events may be responsible of this :
1.- The SSL certificate may be outdated and, then, have to be renewed ;
2.- The dedicated IP of your hosting account is down. A shared IP is used
instead and the certificate is unbindable from this one ;
Regards,
Pierre
Le 18 juin 20
22 matches
Mail list logo
