Skip Menu |

This queue is for tickets about the Net-WebSocket-Server CPAN distribution.

Report information
The Basics
Id: 87768
Status: rejected
Priority: 0/
Queue: Net-WebSocket-Server
People
Owner: TOPAZ [...] cpan.org
Requestors: halgol60 [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sun Aug 11 04:02:11 2013 halgol60 [...] gmail.com - Ticket created
Subject: Attempting to connect via wss kills server!
Date: Sun, 11 Aug 2013 03:01:55 -0500
To: bug-Net-WebSocket-Server [...] rt.cpan.org
From: Hal Goldfarb <halgol60 [...] gmail.com>
I am finding that the server can be killed if one attempts to use a wss: rather than a ws: URI. I can supply the test code if needed, but I think this can be implemented just as easily using an existing setup. I believe this may be related to the other issue I just reported about SSL support: since there is no SSL support currently(?assuming that is the case), there is no way to connect via wss, causing Connection to choke with an error saying a socket is required (meaning the accept() socket, which does not exist in this scenario for some reason). At any rate, the server should not be killable by a "client" (using that term loosely knowing that websockets are more peer-based).
  Mon Aug 12 03:09:43 2013 TOPAZ [...] cpan.org - Taken
  Mon Sep 02 23:11:11 2013 TOPAZ [...] cpan.org - Correspondence added
Could not reproduce. In my test, connecting via "wss://...." in Firefox simply causes the server to close the connection as normal. Please post sample code.
  Mon Sep 02 23:11:12 2013 The RT System itself - Status changed from 'new' to 'open'
  Mon Sep 02 23:11:12 2013 TOPAZ [...] cpan.org - Status changed from 'open' to 'rejected'
  Tue Sep 03 00:12:57 2013 TOPAZ [...] cpan.org - Correspondence added
Just found a similar bug (different cause, same message / location); wait for v0.2.0 and see if that fixes your bug as well.