- From: Shannon <shannon@arc.net.au>
- Date: Wed, 23 Jul 2008 17:08:14 +1000
> > 3.) If the resulting absolute URL has a <port> component, then let port > be that component's value; otherwise, if secure is false, let port be > 81, otherwise let port be 815. > > No, no, no! Don't let paranoia override common sense. Not all websocket > applications will have the luxury to run on these ports (multiple web > servers, shared host, tunnelled connections, 2 websocket apps on one > host, etc...). My mistake. I misread this as *requiring* port 81 and 815. It appears that is not the case. All ports are valid. Shannon
Received on Wednesday, 23 July 2008 00:08:14 UTC