Re: Channels: rejecting web socket connections with a custom close code

Hi Andrew, Thanks for clarifying. I didn't think to look at the ASGI spec but it is described quite well there under the WebSocket/Close section. Thanks for your hard work on this project. Regards, Matt On Saturday, 6 October 2018 10:47:46 UTC+1, Andrew Godwin wrote: > > Hi Matt, > > This

Re: Channels: rejecting web socket connections with a custom close code

hello someone help me i am getting django 404 error ..how fix it ...please help me i am so frustrated On Wednesday, 3 October 2018 04:23:30 UTC-7, Matt F wrote: > > Hello all, > > I have a question about the process of accepting/rejecting web socket > connections in Channels consumers

Re: Channels: rejecting web socket connections with a custom close code

Hi Matt, This is because the two ways of closing are different - closing before the socket is open sends a HTTP error code (what browsers report for this is different in terms of websocket errors), whereas closing once it is open allows a websocket error to be used. This is referenced in the

Channels: rejecting web socket connections with a custom close code

Hello all, I have a question about the process of accepting/rejecting web socket connections in Channels consumers (v2.1.3). I have found that if I have code like this: class MyConsumer(JsonWebsocketConsumer): def connect(self): if authenticated: self.accept()