Django频道/达芙妮中的Web套接字超时

Question

简短的问题版本：我在 Daphne 配置、消费者代码或客户端代码中做错了什么？

channels==1.1.8
daphne==1.3.0
Django==1.11.7

详情如下：

我试图使用Django通道和Daphne接口服务器保持持久的Web套接字连接打开。我使用默认参数启动Daphne：daphne-b0.0.0.0-p 8000my_app.asgi：channel_layer。

我看到在浏览器中闲置一段时间后，连接关闭，时间不超过20秒。与断开连接一起发送的< code>CloseEvent的< code>code值为< code>1006(异常关闭)，未设置< code>reason，并且< code>wasClean设置为false。这应该是服务器关闭连接，而不发送显式关闭帧。

Daphne CLI 具有 --ping 间隔和 --ping 超时标志，默认值分别为 20 秒和 30 秒。对于前者，这被记录为“WebSocket 在发送激活 ping 之前必须处于空闲状态的秒数”，对于后者，则记录为“如果没有响应保持连接 ping 时关闭 WebSocket 之前的秒数”。我读到这个是因为Daphne会等到WebSocket空闲20秒再发送ping，如果30秒后没有收到响应，就会关闭Websocket。相反，我看到的是连接在空闲 20 秒后关闭。（在三次尝试中，默认值，在 20081 毫秒、20026 毫秒和 20032 毫秒之后关闭）

如果我将服务器更改为使用< code > Daphne-b 0 . 0 . 0 . 0-p 8000-ping-interval 10-ping-time out 60 my _ app . asgi:channel _ layer 启动，连接仍然关闭，大约有20秒的空闲时间。(三次尝试更新pings后，在19892毫秒、20011毫秒、19956毫秒后关闭)

以下代码:

消费者.py：

import logging

from channels import Group
from channels.generic.websockets import JsonWebsocketConsumer

from my_app import utilities

logger = logging.getLogger(__name__)

class DemoConsumer(JsonWebsocketConsumer):
    """
    Consumer echos the incoming message to all connected Websockets,
    and attaches the username to the outgoing message.
    """
    channel_session = True
    http_user_and_session = True

    @classmethod
    def decode_json(cls, text):
        return utilities.JSONDecoder.loads(text)

    @classmethod
    def encode_json(cls, content):
        return utilities.JSONEncoder.dumps(content)

    def connection_groups(self, **kwargs):
        return ['demo']

    def connect(self, message, **kwargs):
        super(DemoConsumer, self).connect(message, **kwargs)
        logger.info('Connected to DemoConsumer')

    def disconnect(self, message, **kwargs):
        super(DemoConsumer, self).disconnect(message, **kwargs)
        logger.info('Disconnected from DemoConsumer')

    def receive(self, content, **kwargs):
        super(DemoConsumer, self).receive(content, **kwargs)
        content['user'] = self.message.user.username
        # echo back content to all groups
        for group in self.connection_groups():
            self.group_send(group, content)

routing.py：

from channels.routing import route

from . import consumers

channel_routing = [
    consumers.DemoConsumer.as_route(path=r'^/demo/'),
]

demo.js：

// Tracks the cursor and sends position via a Websocket
// Listens for updated cursor positions and moves an icon to that location
$(function () {
  var socket = new WebSocket('ws://' + window.location.host + '/demo/');
  var icon;
  var moveTimer = null;
  var position = {x: null, y: null};
  var openTime = null;
  var lastTime = null;
  function sendPosition() {
    if (socket.readyState === socket.OPEN) {
      console.log('Sending ' + position.x + ', ' + position.y);
      socket.send(JSON.stringify(position));
      lastTime = Date.now();
    } else {
      console.log('Socket is closed');
    }
    // sending at-most 20Hz
    setTimeout(function () { moveTimer = null; }, 50);
  };
  socket.onopen = function (e) {
    var box = $('#websocket_box');
    icon = $('<div class="pointer_icon"></div>').insertAfter(box);
    box.on('mousemove', function (me) {
      // some browsers will generate these events much closer together
      // rather than overwhelm the server, batch them up and send at a reasonable rate
      if (moveTimer === null) {
        moveTimer = setTimeout(sendPosition, 0);
      }
      position.x = me.offsetX;
      position.y = me.offsetY;
    });
    openTime = lastTime = Date.now();
  };
  socket.onclose = function (e) {
    console.log("!!! CLOSING !!! " + e.code + " " + e.reason + " --" + e.wasClean);
    console.log('Time since open: ' + (Date.now() - openTime) + 'ms');
    console.log('Time since last: ' + (Date.now() - lastTime) + 'ms');
    icon.remove();
  };
  socket.onmessage = function (e) {
    var msg, box_offset;
    console.log(e);
    msg = JSON.parse(e.data);
    box_offset = $('#websocket_box').offset();
    if (msg && Number.isFinite(msg.x) && Number.isFinite(msg.y)) {
      console.log((msg.x + box_offset.left) + ', ' + (msg.y + box_offset.top));
      icon.offset({
        left: msg.x + box_offset.left,
        top: msg.y + box_offset.top
      }).text(msg.user || '');
    }
  };
});

asgi.py：

import os
from channels.asgi import get_channel_layer

os.environ.setdefault("DJANGO_SETTINGS_MODULE", "my_project.settings")

channel_layer = get_channel_layer()

settings.py：

CHANNEL_LAYERS = {
    'default': {
        'BACKEND': 'asgi_redis.RedisChannelLayer',
        'ROUTING': 'main.routing.channel_routing',
        'CONFIG': {
            'hosts': [
                'redis://redis:6379/2',
            ],
            'symmetric_encryption_keys': [
                SECRET_KEY,
            ],
        }
    }
}

Answer 1

根本问题是接口服务器前面的nginx代理。代理设置为proxy_read_timeout 20s 。如果服务器生成了保活ping，则这些ping不会计入上游读取超时。将此超时值增加到更大的值可以使Websocket保持更长的打开时间。我将proxy_connect_timeout和proxy_send_timeou20秒