odd behavior downloading from data loggers
-
I'm revisiting an issue we had three years ago and wondered whether anyone here might have suggestions of possible causes (with testing ideas if possible). We have a work-around but my curious mind has not been satisfied. At work we use some temperature and humidity data loggers. The units (model iTHX-SD) are accessed via ethernet and have a web server that allows the user to download data covering a day, week, month or year, saving to a text/csv file. In Oct. 2019 our weekly downloads using Chrome stopped working (around the same time Chrome 78.0.3904 was released). Chrome's download would show "Failed - No File." Facts and testing from around that time showed: 1. The issue occurred the same week at two different facilities and with various computers, including Chrome on Win 10, Win 7, Linux and Android phone. Note, though, that only one computer attempted (and succeeded) to access the data the prior week. 2. Firmware for the loggers had not changed. 3. We could download a day's worth of data, but not a week's worth. Previously we had no trouble downloading a year's worth of data. 4. Firefox and Edge can download the data (our work-around). 5. Chrome, IE and Opera failed to download the data, with Opera reporting that the download was interrupted. (IE and Opera were not used for this prior to this test, so no idea how they 'previously' behaved.) 6. In April 2020 I tried downloading a year's worth of data with Chrome 81.0.4044 and the progress bar showed 28.4/28.4 MB for a fraction of a second before showing Failed - No File. 7. In May 2020 I was able to download a 299,599 byte file but failed with a 300,219 byte file (size based on successful download using Edge). Larger files usually fail at the end of the download but can stall late in the download. I'd love any input on possible causes and/or tests to try. Unfortunately, I don't know (or have) the logger's firmware code. As I said, at this point I'm trying to satisfy my curiosity, which will allow me to close this out.
-
I'm revisiting an issue we had three years ago and wondered whether anyone here might have suggestions of possible causes (with testing ideas if possible). We have a work-around but my curious mind has not been satisfied. At work we use some temperature and humidity data loggers. The units (model iTHX-SD) are accessed via ethernet and have a web server that allows the user to download data covering a day, week, month or year, saving to a text/csv file. In Oct. 2019 our weekly downloads using Chrome stopped working (around the same time Chrome 78.0.3904 was released). Chrome's download would show "Failed - No File." Facts and testing from around that time showed: 1. The issue occurred the same week at two different facilities and with various computers, including Chrome on Win 10, Win 7, Linux and Android phone. Note, though, that only one computer attempted (and succeeded) to access the data the prior week. 2. Firmware for the loggers had not changed. 3. We could download a day's worth of data, but not a week's worth. Previously we had no trouble downloading a year's worth of data. 4. Firefox and Edge can download the data (our work-around). 5. Chrome, IE and Opera failed to download the data, with Opera reporting that the download was interrupted. (IE and Opera were not used for this prior to this test, so no idea how they 'previously' behaved.) 6. In April 2020 I tried downloading a year's worth of data with Chrome 81.0.4044 and the progress bar showed 28.4/28.4 MB for a fraction of a second before showing Failed - No File. 7. In May 2020 I was able to download a 299,599 byte file but failed with a 300,219 byte file (size based on successful download using Edge). Larger files usually fail at the end of the download but can stall late in the download. I'd love any input on possible causes and/or tests to try. Unfortunately, I don't know (or have) the logger's firmware code. As I said, at this point I'm trying to satisfy my curiosity, which will allow me to close this out.
JRickey wrote:
Chrome's download would show "Failed - No File."
I briefly looked into this for you and the Chromium source code reveals that the error
DOWNLOAD_INTERRUPT_REASON_SERVER_BAD_CONTENTresults in the "Failed - No File." message. Following that code path... [https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#281\](https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#281) It checks that the webserver responds with code 206, if not it returns an error. Continuing... it then validates the Content-Range header. [https://chromium.googlesource.com/chromium/src/+/lkgr/net/http/http\_response\_headers.h#319\](https://chromium.googlesource.com/chromium/src/+/lkgr/net/http/http\_response\_headers.h#319) [https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#286\](https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#286) You could debug this with [Wireshark](https://www.wireshark.org/download.html) to see if the webserver is sending back a valid Content-Range header. This is the Lounge where people hang out and chat, look up at the top of the site and post something in "Quick Answers" if you have anymore questions. -
I'm revisiting an issue we had three years ago and wondered whether anyone here might have suggestions of possible causes (with testing ideas if possible). We have a work-around but my curious mind has not been satisfied. At work we use some temperature and humidity data loggers. The units (model iTHX-SD) are accessed via ethernet and have a web server that allows the user to download data covering a day, week, month or year, saving to a text/csv file. In Oct. 2019 our weekly downloads using Chrome stopped working (around the same time Chrome 78.0.3904 was released). Chrome's download would show "Failed - No File." Facts and testing from around that time showed: 1. The issue occurred the same week at two different facilities and with various computers, including Chrome on Win 10, Win 7, Linux and Android phone. Note, though, that only one computer attempted (and succeeded) to access the data the prior week. 2. Firmware for the loggers had not changed. 3. We could download a day's worth of data, but not a week's worth. Previously we had no trouble downloading a year's worth of data. 4. Firefox and Edge can download the data (our work-around). 5. Chrome, IE and Opera failed to download the data, with Opera reporting that the download was interrupted. (IE and Opera were not used for this prior to this test, so no idea how they 'previously' behaved.) 6. In April 2020 I tried downloading a year's worth of data with Chrome 81.0.4044 and the progress bar showed 28.4/28.4 MB for a fraction of a second before showing Failed - No File. 7. In May 2020 I was able to download a 299,599 byte file but failed with a 300,219 byte file (size based on successful download using Edge). Larger files usually fail at the end of the download but can stall late in the download. I'd love any input on possible causes and/or tests to try. Unfortunately, I don't know (or have) the logger's firmware code. As I said, at this point I'm trying to satisfy my curiosity, which will allow me to close this out.
"Browser incompatibility". The server is returning (or Chrome is expecting) a code / event that only Edge and Firefox are "handling" (or ignoring) as the case my be. I'd look at FTP.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
JRickey wrote:
Chrome's download would show "Failed - No File."
I briefly looked into this for you and the Chromium source code reveals that the error
DOWNLOAD_INTERRUPT_REASON_SERVER_BAD_CONTENTresults in the "Failed - No File." message. Following that code path... [https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#281\](https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#281) It checks that the webserver responds with code 206, if not it returns an error. Continuing... it then validates the Content-Range header. [https://chromium.googlesource.com/chromium/src/+/lkgr/net/http/http\_response\_headers.h#319\](https://chromium.googlesource.com/chromium/src/+/lkgr/net/http/http\_response\_headers.h#319) [https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#286\](https://chromium.googlesource.com/chromium/src/+/49bbefe192eabd120f9af9aa1e18ab0116cce891/components/download/internal/common/download\_utils.cc#286) You could debug this with [Wireshark](https://www.wireshark.org/download.html) to see if the webserver is sending back a valid Content-Range header. This is the Lounge where people hang out and chat, look up at the top of the site and post something in "Quick Answers" if you have anymore questions. -
"Browser incompatibility". The server is returning (or Chrome is expecting) a code / event that only Edge and Firefox are "handling" (or ignoring) as the case my be. I'd look at FTP.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
I'm curious what the incompatibility is. As for FTP the firmware does not seem to allow that. What I'm working on is code to submit the HttpRequest, retrieve the data, parse it and save to a database (simple steps, now that I know how to form the request). I was just hoping to get an idea of the cause in order to satisfy my curiosity.
-
Thanks, @Randor. I have minimal experience with Wireshark but I did get it to log some data. I'm not seeing any apparent cause, but I'll continue looking.