On 30-11-2012 16:00, Camillo Bruni wrote:
interesting :) can you figure out your proxy configuration? this is very strange :P

Proxy Test

This request appears to have come via a proxy.

The proxy host is ex1.lsi.usp.br which has ip address 143.107.161.170

The proxy server has announced itself as 1.1 gate.lsi.usp.br (squid/3.0.STABLE18)

The proxy informs us that the client host ip address was 10.0.164.156

 

The Lagado Proxy Test shows details of any proxy servers you are using. It is especially useful to expose transparent proxies. These are proxies inserted between your browser and the web, typically by your ISP, and often without you knowing.

Sometimes a proxy will be deliberately hidden so it won't be exposed by this test. In this case you can use the Cache Test to expose stealthed transparent proxy caches.

 

The Raw Details

Here are the raw details of the request received by this server.

Remote   Host ex1.lsi.usp.br   IP Address 143.107.161.170

Request   Protocol HTTP/1.0   Method GET

Request Headers
Host www.lagado.com
User-Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.91 Safari/537.11
Accept text/html,​application/xhtml+xml,​application/xml;q=0.9,​ */*;q=0.8
Referer http://www.lagado.com/text/tools_b7f5.htm
Accept-Encoding gzip,deflate,sdch
Accept-Language pt-BR,pt;q=0.8,en-US;q=0.6,en;q=0.4
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.3
Via 1.1 gate.lsi.usp.br (squid/3.0.STABLE18)
X-Forwarded-For 10.0.164.156
Cache-Control max-age=259200
Connection keep-alive

This Server   Host www.lagado.com   IP Address 210.50.6.232

Date: Saturday 1 Dec 2012 5:31:44 GMT+1100




On 2012-11-30, at 14:33, Casimiro de Almeida Barreto <casimiro.barreto@gmail.com> wrote:


On 30-11-2012 15:24, Camillo Bruni wrote:

most probably https://code.google.com/p/pharo/issues/detail?id=6986

are you behind a proxy?

Yes, seems to be the problem just as reported in issues #6986

On 2012-11-30, at 14:13, Casimiro de Almeida Barreto <casimiro.barreto@gmail.com> wrote:


I've had strange problem with Pharo 2.0: it times out at Gofer. For
instance:

Gofer new
  squeaksource: 'MetacelloRepository';
  package: 'ConfigurationOfSeaside30';
  load.

Will spend the 30secs timeout & then give-me a debugger window
complaining that could not connect. But network is OK and Pharo 1.4 does
not have this problem. Besides, Pharo 2.0 updates OK (so, again, there's
no network problem).

CdAB