RE: error frozenice found

Hey Renoir,


I just checked it (busy day), it's different now, but not fine. :( Now we get a 400 when connecting to the WebSocket. You can see that on the normal pages too, btw. Just check the Network tab on Chrome DevTools and look for the __streamer__ websocket call.


I captured the packet to see what else it says besides 400 (sadly, the DevTools don't show that and I didn’t find anything in our server-logs):

400 Bad Request

The server could not comply with the request since it is either malformed or otherwise incorrect.

Can "Upgrade" only to "WebSocket".


Some googling shows code which checks if the Upgrade HTTP header lowercase-equals “websocket”.


Maybe that header doesn’t get passed along by Fastly or nginx?




-----Original Message-----
From: Renoir Boulanger [] 
Sent: Samstag, 19. April 2014 03:34
To: David Kirstein; List WebPlatform public
Subject: error frozenice found


Hey Fro—


I'd like to know if you still see the error related to annotation server.


The code has been upgraded and I also adjusted NGINX proxy settings, it

seems fine.


Keep me posted.





Renoir Boulanger  |  Developer operations engineer

W3C  |  Web Platform Project


 <>  ✪   <>  ✪  @renoirb




Received on Saturday, 19 April 2014 20:21:31 UTC