WebClient + SqueakSSL = https

> Folks -
>
> I've added the first round of https support for WebClient and I'm looking for
> beta testers / feedback. In particular if you're set up using
> (authenticating) proxies I'm curious whether WebClient behaves correctly.
> Assuming you've set up your Squeak environment, all you need is to:
>
> * Install the SqueakSSL plugin:
>  http://squeakvm.org/win32/release/SqueakSSL.zip
>
> * Install SqueakSSL:
>  (Installer ss)
>      project: 'SqueakSSL';
>      install: 'SqueakSSL-Core';
>      install: 'SqueakSSL-Tests'.
>
> * Install WebClient:
>  (Installer ss)
>      project: 'WebClient';
>      install: 'WebClient-Core';
>      install: 'WebClient-Tests';
>      install: 'WebClient-Help'.
>
> Once installed, you can use the following to test SqueakSSL:
>
>  WebClient httpGet: 'https://www.google.com/search?q=squeak'.
>
> If this works everything is set up properly. If you encounter any problems
> accessing your favorite SSL sites, let me know.

> On Sun, 25 Jul 2010, Andreas Raab wrote:
>
>> On 7/25/2010 7:55 PM, Levente Uzonyi wrote:
>>> It works for me, but I always get 'Invalid certificate' error, even for
>>> google.com. #certState is always 1 (generic error). If I just ignore the
>>> error, everything is fine. Is there a way to debug it?
>>> (Ubuntu 8.04 x86_64 CogVM)
>>
>> Interesting. I suspect it's something in OpenSSL plugin code. The thing to
>> try is to to change SecureSocketStream>>sslConnect from:
>>
>> squeakSSL := SqueakSSL new.
>>
>> to the following:
>>
>> squeakSSL := SqueakSSL new.
>>
>> "Logs extra info stdout"
>> squeakSSL logLevel: 1.
>>
>> You should be getting a bunch of console output as a result which should
>> prove helpful.
>
> I found a few issues with logging on unix:
> - SqueakSSL >> #primitiveSSL:setIntProperty:toValue: calls
>  #primitiveSetStringProperty instead of #primitiveSetIntProperty.
> - #primitiveSetIntPropery always fails, because sqSetIntPropertySSL always
>  returns 0, it should return 1 at the end of the function.
> After fixing these #logLevel: with argument 1 didn't give any output. It
> works with 2 and 3. It's a bit annoying that the log messages are not flushed
> (printf is buffered), so one has to generate a few requests to see the result
> of the first one (I can't flush stdout without FFI or OSProcess).
>
>>
>> Also, you might try to see whether going directly to encrypted.google.com
>> makes a difference (the https request to www.google.com is first redirected
>> to encrypted.google.com and perhaps the problem is somewhere in the
>> redirect handling):
>>
>> WebClient httpGet: 'https://encrypted.google.com/search?q=squeak'.
>
> It's the same.
>
> I attached the output of [WebClient httpGet:
> 'https://www.google.com/search?q=squeak'] generated with #logLevel: 3.

> I found a few issues with logging on unix:
> - SqueakSSL >> #primitiveSSL:setIntProperty:toValue: calls
> #primitiveSetStringProperty instead of #primitiveSetIntProperty.
> - #primitiveSetIntPropery always fails, because sqSetIntPropertySSL always
> returns 0, it should return 1 at the end of the function.
> After fixing these #logLevel: with argument 1 didn't give any output. It
> works with 2 and 3. It's a bit annoying that the log messages are not
> flushed (printf is buffered), so one has to generate a few requests to
> see the result of the first one (I can't flush stdout without FFI or
> OSProcess).

> On 7/26/2010 6:59 AM, Levente Uzonyi wrote:
>> I found a few issues with logging on unix:
>> - SqueakSSL >> #primitiveSSL:setIntProperty:toValue: calls
>> #primitiveSetStringProperty instead of #primitiveSetIntProperty.
>> - #primitiveSetIntPropery always fails, because sqSetIntPropertySSL always
>> returns 0, it should return 1 at the end of the function.
>> After fixing these #logLevel: with argument 1 didn't give any output. It
>> works with 2 and 3. It's a bit annoying that the log messages are not
>> flushed (printf is buffered), so one has to generate a few requests to
>> see the result of the first one (I can't flush stdout without FFI or
>> OSProcess).
>
> Thanks, I will fix that. For some reason the output in my Ubuntu is

>
>> I attached the output of [WebClient httpGet:
>> 'https://www.google.com/search?q=squeak'] generated with #logLevel: 3.
>
> Your analysis in the other email is correct. The error code means the CA
> certs are missing and installing them should fix the problem.
>
> Cheers,
>  - Andreas
>
>

> On Mon, 26 Jul 2010, Andreas Raab wrote:
>
>> On 7/26/2010 6:59 AM, Levente Uzonyi wrote:
>>> It's a bit annoying that the log messages are not
>>> flushed (printf is buffered), so one has to generate a few requests to
>>> see the result of the first one (I can't flush stdout without FFI or
>>> OSProcess).
>>
>> Thanks, I will fix that. For some reason the output in my Ubuntu is
>> unbuffered; any ideas why that would be?
>
> Not really. IIRC printf should automatically flush on \n, but it somehow doesn't do it.

> On Mon, 26 Jul 2010, Andreas Raab wrote:
>
>> On 7/26/2010 6:59 AM, Levente Uzonyi wrote:
>>> I found a few issues with logging on unix:
>>> - SqueakSSL >> #primitiveSSL:setIntProperty:toValue: calls
>>> #primitiveSetStringProperty instead of #primitiveSetIntProperty.
>>> - #primitiveSetIntPropery always fails, because sqSetIntPropertySSL always
>>> returns 0, it should return 1 at the end of the function.
>>> After fixing these #logLevel: with argument 1 didn't give any output. It
>>> works with 2 and 3. It's a bit annoying that the log messages are not
>>> flushed (printf is buffered), so one has to generate a few requests to
>>> see the result of the first one (I can't flush stdout without FFI or
>>> OSProcess).
>>
>> Thanks, I will fix that. For some reason the output in my Ubuntu is
>
> Thanks.
>
>> unbuffered; any ideas why that would be?
>
> Not really. IIRC printf should automatically flush on \n, but it somehow
> doesn't do it.

>
>
> Levente
>
>>
>>> I attached the output of [WebClient httpGet:
>>> 'https://www.google.com/search?q=squeak'] generated with #logLevel: 3.
>>
>> Your analysis in the other email is correct. The error code means the CA
>> certs are missing and installing them should fix the problem.
>>
>> Cheers,
>>  - Andreas
>>
>>
>
>