[AWS] Bug found in the AWS WebSocket implementation

Thomas Løcke thomas.granvej6 at gmail.com
Thu Aug 29 12:39:47 CEST 2013


You already have a small and simple standalone reproducer: The AWS hello
world demo. That was what I used to verify that something indeed was rotten
in the state of Denmark.

All you need to do is fire it up and make one minor change to
aws/demos/websockets/page.thtml.
Or am I missing something?

:o)


2013/8/29 Pascal Obry <pascal at obry.net>

>
> Thomas,
> > Is there a way to solve this? Have I found a bug? AFAIK this is not how
> > websockets are supposed to behave. Trying to connect to other
> > implementations I usually get a plain 404 dumped on me if I try to
> > connect to unknown addresses.
>
> Looks like a bug indeed. It can probably be solved at the time we
> connect and check for the proper WebSocket constructor. Would be nice to
> setup a small standalone reproducer, it will help a lot!
>
> Thanks,
>
> --
>   Pascal Obry /  Magny Les Hameaux (78)
>
>   The best way to travel is by means of imagination
>
>   http://v2p.fr.eu.org
>   http://www.obry.net
>
>   gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/aws/attachments/20130829/a4fbfb35/attachment.html>


More information about the AWS mailing list