From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 11:00 PM CDT Friday, Nov 8 - 2:30 PM CDT Saturday, Nov 9, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
09-23-2017 01:17 PM
There are two attachments in another thread (here and here) that cannot be downloaded using chrome. I wrote some of my suspicions here, but of course I am not sure what the problem really is.
Note that this is a chrome problem. If I try to download using edge browser, it works just fine.
The question is if this is due to a bug in chrome or due to some nonstandard html that edge can gloss over but chrome does more rigorous checking and rejects the download.
Should I report this using the chrome feedback tool ("report an issue") or should lithium investigate first?
09-23-2017 01:32 PM
The same complaint has been happening in the LabVIEW Architects board as presentations from the CLA Summit are being posted. Those using Chrome have not been able to download. Using Firefox, I have had no issues at all.
09-23-2017 01:40 PM
Do these other attachments also have a collection of delimiters as part of the file name?
(I submitted some feedback to the chrome team so they can investigate on their end.)
09-23-2017 06:17 PM
@altenbach wrote:
Do these other attachments also have a collection of delimiters as part of the file name?
They do have spaces. I think most were ppt or pptx files. There might be a PDF in there.
09-23-2017 07:24 PM - edited 09-23-2017 07:35 PM
A google search for "err_response_headers_multiple_content_disposition chrome" has quite a few hits and some indicate that filenames with commas ( , ) or semicolons ( ; ) are a problem. Most seem to have solutions to be implemented on the server side (example). I guess lithium needs to fix that.
09-25-2017 01:49 PM
Hi altenbach,
Thank you for reporting this issue.
As you've noted this is related to the inclusion of a comma in the filename and how the Chrome browser handles commas in file attachments. From what I have found it appears this is a somewhat common issue, but there will be no fix from Chrome and this must be addressed on our side.
We will raise this issue to our community provider to request a fix.
Thanks again!