transmitting file from server not working
Reported by
nagur...@gmail.com,
Sep 20 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Example URL: Steps to reproduce the problem: 1. when i click button from my website file not transmitted to local machine 2. existing version it works fine 3. response.close code was not working in this version.tried for so many ways. What is the expected behavior? What went wrong? unable to work on our reports Did this work before? N/A Chrome version: 53.0.2785.116 Channel: stable OS Version: 6.3 Flash Version: Shockwave Flash 23.0 r0
,
Sep 22 2016
The issue is that your server is sending an invalid response. It's trying to send a chunked response, but doesn't send a terminal chunk. As a result, Chrome doesn't know if the entire response has been received, or if the socket was erroneously closed. Chrome used to incorrectly consider such transfers successes, but we've since fixed that bug. You have a couple options to fix this: 1) Send the terminal chunk(0\r\n\r\n, I believe). Then you could even not close the socket, and reuse it for future requests, if you wanted. 2) Don't send the response using chunked encoding. This would technically make it an HTTP/1.0 response, I believe, though should work even if you continue to claim it's an HTTP/1.1 response. 3) Send Content-Length and don't use chunked encoding. If you don't know it in advance, obviously you can't do this (Unless oyu delay sending the headers until you know the content length). Also worth noting that if connections can't be reused, you're best off sending a "Connection: Close" header, or advertising the response as HTTP/1.0. |
||
►
Sign in to add a comment |
||
Comment 1 by ckrasic@chromium.org
, Sep 20 2016