W3C home > Mailing lists > Public > public-webplatform@w3.org > April 2014

Re: Notes.webplatform.org error frozenice found

From: Renoir Boulanger <renoir@w3.org>
Date: Sat, 19 Apr 2014 21:19:56 -0400
Message-ID: <535320BC.6080709@w3.org>
To: David Kirstein <frozenice@frozenice.de>, 'List WebPlatform public' <public-webplatform@w3.org>
Hi Fro

I just upgraded the notes.webplatform.org webserver. It is now under
Ubuntu 14.04 LTS (released this week) and is now running with NGINX 1.4
which supports WebSocket protocol upgrade.

Tell me if you see any other kinks.

Renoir
~



On 2014-04-19, 4:21 PM, David Kirstein wrote:
> 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?
>
>  
>
> -fro
>
>  
>
> -----Original Message-----
> From: Renoir Boulanger [mailto:renoir@w3.org] 
> Sent: Samstag, 19. April 2014 03:34
> To: David Kirstein; List WebPlatform public
> Subject: Notes.webplatform.org error frozenice found
>
>  
>
> Hey Fro—
>
>  
>
> I'd like to know if you still see the error related to
>
> notes.webplatform.org annotation server.
>
>  
>
> The code has been upgraded and I also adjusted NGINX proxy settings, it
>
> seems fine.
>
>  
>
> Keep me posted.



Received on Sunday, 20 April 2014 01:20:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:20:58 UTC