Document part does not display document when original filename has commas in it

James Angus

Document part is not quoting the `content-disposition: filename=` header when displaying a document (e.g. PDF). This causes the browser to error and not display a document that has a comma in the name.



Here is an example:



$> curl -I http://mywebaddress.com/document.doc?...


HTTP/1.1 200 OK


Cache-Control: private


Content-Length: 346254


Content-Type: application/pdf


Last-Modified: Thu, 16 May 2013 22:38:37 GMT


Set-Cookie: ASP.NET_SessionId=0000000000000; path=/; HttpOnly


title: Role Statement - systems admin programmer


content-disposition: filename=IT Systems Administrator, Programmer role statement April 2013.pdf


X-AspNet-Version: 4.0.30319


X-Powered-By: ASP.NET


Date: Sun, 19 May 2013 22:56:55 GMT



To counteract this issue, the filename header should be double-quoted.


The BBNC version I encountered this issue on is: 6.45.2034.44

Karen Badham

Hey Ejangi,



This doesn't seem to be working as designed, so we need a case to be able to move forward with fixing it. I can't find anyone in our database with the first name Ejangi, so please create a case on case central. http://www.blackbaud.com/support/case...



Thanks!


Karen

James Angus

Okay, I have created a case. Thanks.