We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Websocket Behavior

  • 4 antwoorde
  • 1 het hierdie probleem
  • 6 views
  • Laaste antwoord deur rogerfgay

rogerfgay
rogerfgay
more options

Websocket behavior.

Beta 7: Browser throws error instead of processing message returned from close request.

Beta 7.01 and 8: Browser causes null pointer error on server (malformed message) when dealing with characters outside the UTF8 character set. Also, Beta 7 problem above not yet fixed.

Websocket behavior. Beta 7: Browser throws error instead of processing message returned from close request. Beta 7.01 and 8: Browser causes null pointer error on server (malformed message) when dealing with characters outside the UTF8 character set. Also, Beta 7 problem above not yet fixed.

All Replies (4)

John99
John99
more options

What exactly are you trying to discus ? http://en.wikipedia.org/wiki/WebSocket

Bugs: https://bugzilla.mozilla.org/

Also have a look through some of the kb s eg

Gewysig op deur John99

rogerfgay
rogerfgay Vraag-eienaar
more options

I posted more information in the steps taken section of the original post, which I'm surprised was not published. I'm running this test page: http://isr.nu/ws/WebSocketTest.htm

Note the difference if you run it in Firefox (beta 7 or above) verses Chromium (Chrome dev-channel v14 or above).

Using Chrome, you'll see that the message from the server ("bye") is displayed when you close the connection. In Firefox, you get an ERROR instead.

Since posting here, I found my way to Bugzilla and reported this.

Gewysig op deur rogerfgay

John99
John99
more options

Apparently as Bug 691038

What are you trying to say that the page is faulty ?

If I follow your link then take the close connection option from the button on the Left Hand Side of the page, then the right hand side displays NOT CONNECTED in red, which may be the expected behavior.

I am currently using Windows XP SP3 and Firefox 9.0a2

Gewysig op deur John99

rogerfgay
rogerfgay Vraag-eienaar
more options

This is the same comment made on Bug 691038 yesterday, which I already answered. You need to connect before you disconnect (close).