CocoaVMs DO NOT automatically recognize proxy settings of MacOS

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

CocoaVMs DO NOT automatically recognize proxy settings of MacOS

Mariano Martinez Peck
 
Hi guys. The VMs for Carbon, both build with CMakeVMMaker or the ones from Eliot, do automatically recognize the proxy settings in the network preferences of MacOS. So, the images work out of the when going to internet.

However, CocoaVMs (tested building with CMakeVMMAker) don't do that, and in fact, you have to explicitly set the proxy, by using HTTPSocket proxyUser: userName password: password    or using the Pharo Settings.

Here at work I have a proxy...setting manually everytime I open an image is not funny. Even more, if I then try to open it at home (where I don't have a proxy), of course it doesn't work, so I need to reset the settings.

So....anyone has a clue where such differences can be?  what can be done?

thanks in advance

--
Mariano
http://marianopeck.wordpress.com

Reply | Threaded
Open this post in threaded view
|

Re: CocoaVMs DO NOT automatically recognize proxy settings of MacOS

EstebanLM
 
hi Mariano, 
please, fill a ticket :)

best,
Esteban

El 04/05/2011, a las 12:29p.m., Mariano Martinez Peck escribió:

Hi guys. The VMs for Carbon, both build with CMakeVMMaker or the ones from Eliot, do automatically recognize the proxy settings in the network preferences of MacOS. So, the images work out of the when going to internet.

However, CocoaVMs (tested building with CMakeVMMAker) don't do that, and in fact, you have to explicitly set the proxy, by using HTTPSocket proxyUser: userName password: password    or using the Pharo Settings.

Here at work I have a proxy...setting manually everytime I open an image is not funny. Even more, if I then try to open it at home (where I don't have a proxy), of course it doesn't work, so I need to reset the settings.

So....anyone has a clue where such differences can be?  what can be done?

thanks in advance

--
Mariano
http://marianopeck.wordpress.com


Reply | Threaded
Open this post in threaded view
|

Re: CocoaVMs DO NOT automatically recognize proxy settings of MacOS

Mariano Martinez Peck
 
http://code.google.com/p/cog/issues/detail?id=42

what a great issue number :)

On Wed, May 4, 2011 at 5:41 PM, Esteban Lorenzano <[hidden email]> wrote:
 
hi Mariano, 
please, fill a ticket :)

best,
Esteban

El 04/05/2011, a las 12:29p.m., Mariano Martinez Peck escribió:

Hi guys. The VMs for Carbon, both build with CMakeVMMaker or the ones from Eliot, do automatically recognize the proxy settings in the network preferences of MacOS. So, the images work out of the when going to internet.

However, CocoaVMs (tested building with CMakeVMMAker) don't do that, and in fact, you have to explicitly set the proxy, by using HTTPSocket proxyUser: userName password: password    or using the Pharo Settings.

Here at work I have a proxy...setting manually everytime I open an image is not funny. Even more, if I then try to open it at home (where I don't have a proxy), of course it doesn't work, so I need to reset the settings.

So....anyone has a clue where such differences can be?  what can be done?

thanks in advance

--
Mariano
http://marianopeck.wordpress.com






--
Mariano
http://marianopeck.wordpress.com

Reply | Threaded
Open this post in threaded view
|

Re: CocoaVMs DO NOT automatically recognize proxy settings of MacOS

johnmci
In reply to this post by Mariano Martinez Peck
 
Mmmm I think a clue would be to follow where the locale plugin is,
since that is used to get the proxy info. Carbon one has is, I'll bet
the cocoa one does not have the new cocoa based one I. Built last
year?

On Wednesday, May 4, 2011, Mariano Martinez Peck <[hidden email]> wrote:
>

--
===========================================================================
John M. McIntosh <[hidden email]>
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
===========================================================================