I can't get it to load mysql on my centos system ?
On Wed, Jan 23, 2019, 9:46 AM Hey I read the spec of websocket handshake and I believe that in abrupt
> close connection, the server can send either a 403 or 404. I wish there
> were a way to send a 404. :(
>
> On Sunday, June 24, 2018 at 7:21:10
Hey I read the spec of websocket handshake and I believe that in abrupt
close connection, the server can send either a 403 or 404. I wish there
were a way to send a 404. :(
On Sunday, June 24, 2018 at 7:21:10 PM UTC+2, Andrew Godwin wrote:
>
> I'm not quite sure - WebSockets do have browser diff
I'm not quite sure - WebSockets do have browser differences. You could also
try adding a delay between the accept and the close to see if that changes
how they handle it.
Andrew
On Sun, 24 Jun 2018, 06:02 Kirill Tyushchakov,
wrote:
> Hi, Andrew! Thanks a lot for your response.
> I've changed my
Hi, Andrew! Thanks a lot for your response.
I've changed my consumer's connect method like this:
def connect(self):
user = self.scope.get('user')
super(NotificationsConsumer, self).connect()
if user.is_anonymous:
self.close(code=4003)
I've tested it in Chrome, Firefox, Safar
Hi!
Close code 1006 means that the connection was closed abruptly by the other
end (basically, the socket just got chopped off without an actual close
frame being sent).
This is what happens when you close during the handshake, which is what
closing during connect() does - at that point, the conn
Hello everyone!
I'm new in Django Channels. I'm using Channels 2.0 and I have few questions
about it.
I'm using JsonWebsocketConsumer class for my consumer and I wrote my
definition of connect method like this:
def connect(self):
user = self.scope.get('user')
if user.is_anonymous:
6 matches
Mail list logo
