On 10/28/10 11:01 PM, Sean P. DeNigris wrote:
>
> Yanni Chiu wrote:
>> - It's really 8090 (that's a nine), not 8080?
>>
> Yes, I kept changing it to make sure it wasn't a problem with that
> particular port
>
>
> Yanni Chiu wrote:
>> - Are there any proxy configurations involved
>>
> I don't know what that means, but for more context, I started a Ruby
> TCPServer on that port, and then tried to "get" from Squeak, then from
> Safari
Can you "get" using Squeak on any port from the Ruby TCPServer?   
Different scripting libraries can have oddities that the more mainstream 
c-based ones don't have. I once found an error in the Mac's Python TCP 
client code that randomly prepended header data into  xmlrpc content. 
Its possible that Ruby is doing something that Safari libs are robust 
enough to compensate for, or its possible that Ruby is just fine and 
there's an obscure bug in the Squeak lib that you happen to be the first 
to find.

Lawson