QUIC - Not sending full image content in response.

Discussion in 'Bug Reports' started by Karl, Jan 31, 2018.

  1. Karl

    Karl Active Member

    The dreaded:
    Code:
    net::ERR_QUIC_PROTOCOL_ERROR
    This occurs sometimes on 1st page load of a site, a number of the images will fail to load.

    Looking in developer tools in Chrome we see the quic error. Which seemingly results in the full image data not being sent in response:

    Response header says:
    Code:
    accept-ranges bytes
    alt-svc quic=":443"; ma=2592000; v="35,37,38,39"
    cache-control public, max-age=31536000
    content-length 425391
    content-type image/jpeg
    date Wed, 31 Jan 2018 09:54:14 GMT
    expires Thu, 31 Jan 2019 09:54:14 GMT
    last-modified Tue, 30 Jan 2018 13:56:38 GMT
    status 200
    strict-transport-security max-age=31536000
    x-content-type-options nosniff
    x-frame-options sameorigin
    
    The content actually returned is 0 bytes. This is confirmed by the server log:
    Code:
    <snip? - - [31/Jan/2018:09:42:26 +0000] "GET <snip>1372326053.jpg HTTP/1.1" 206 0 "https://<snip>/" "Mozilla/5.0 (Linux; Android 6.0.1; FP2 Build/FP2-gms-17.12.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.111 Mobile Safari/537.36"
    
    Response is served to browser as:
    Code:
    http/2.0+quic/39
    
    We've also seen partial sends as well as 0 byte sends.

    Looking in the error log we see nothing related to that request.

    Version: 5.2.3 Build 7 Enterprise
    OS: CentOS 6 64bit

    Browsers: Chrome - Mobile and Desktop
     
  2. Jon K

    Jon K Administrator Staff Member

    Please try upgrading to 5.2.4 which was released yesterday. In the later builds of 5.2.3 we fixed multiple QUIC issues like you describe here.

    You can upgrade with the following:
    Code:
    /usr/local/lsws/admin/misc/lsup.sh -f -v 5.2.4
     

Share This Page