Monday, March 12, 2012

Error 349 (net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION): Multiple Content-Disposition headers received

SkyHi @ Monday, March 12, 2012
I've just been looking at the similar issue.  After spending the best part of a day and a half stripping back our app.  It finally turned out to be an issue with us setting  "Content-Disposition" in the response header.  I had originally used a sample provided by someone else which had a comma instead of a semi colon between type and file name.  For Example: 

Incorrect Header: Response.AddHeader("Content-Disposition", "attachment, filename=\"" + filename + "\""); 
Correct Header: Response.AddHeader("Content-Disposition", "attachment; filename=\"" + filename + "\""); 

This caused two issues for us.  Using a jQueryFileUpload it would not display a list of existing file and the issue you explained.  This only seems to have happened since 16.0.912.63 as I reverted back to an offline version I had downloaded some time back and it did not exhibit the same errors.  IE and Firefox are not affected ans seem to handle this.

Ah, very nice - The patch fixed the problem. It was using a semicolon already, but there was a comma used in the filename and it was unquoted. 

header("Content-Disposition: inline; filename=vCard_".$this->last_name.",".$this->first_name.".vcf"); 

header("Content-Disposition: inline; filename=\"vCard_".$this->last_name.",".$this->first_name.".vcf\"");