Re[2]: [jetty-user] Work-around for websockets under Ubuntu

Yes, I saw that discussion and no, I do not have my Chrome set up to use a Proxy.

Thanks for trying to help.

Chris



On Sunday, January 30, 2011 at 7:06:45 PM, John Tamplin wrote:
> On Sun, Jan 30, 2011 at 7:10 AM, Chris Haynes <[email protected]>wrote:

>> Just a note to anyone attempting to test Jetty's WebSockets under Ubuntu
>> 10.04 with client and server running on the same machine.

>> It seems that you cannot use 'localhost' or its numeric equivalents
>> under (only?) this version of Ubuntu - Jetty (and a JS-based  webSocket
>> server I tried in desperation) don't receive the connection request.

>> In the client you have to use the 'real' address of the machine (as
>> shown by 'ifconfig') and, to circumvent Jetty's block against testing
>> from what now appears to it to to be a  'remote' machine you have to
>> call the test page directly; in my case: http://192.168.0.3:8080/ws/

>> If anyone knows why Ubuntu is being so uncooperative and how to get it
>> to play nicely, please do let us know; this has taken me 8 hours to work
>> around.

>> In case it is relevant, I am using Chrome 5.0.342.9 beta
>> .
>> The hint which gave me the solution was posted by bradleym06 here:
>> http://code.google.com/p/chromium/issues/detail?id=35101


> From the discussion in that bug, the issue is you have Chrome setup to send
> connections through a proxy.  localhost/127.0.0.1 has meaning only on the
> machine where the connection originated, so if you send the request to a
> proxy at best you get a connection to the proxy machine, which isn't what
> you want.  Your proxy configuration should exclude 127.0.0.0/8 and localhost
> from proxying


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email