The way the gdata api handles non-ascii characters in the content disposition
header breaks the document export functionality. The
Google.GData.Client.GDataRequest.Execute method uses a .NET library to parse
the Content-Disposition field. Since the api returns non-ASCII chars, the
request throws an exception: "The specified content disposition is invalid."
I created an issue in the apps-api issue list. Please see below.
https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3412&tha
nks=3412&ts=1371868519
Original issue reported on code.google.com by ed...@edwinlandy.com on 22 Jun 2013 at 2:41
Original issue reported on code.google.com by
ed...@edwinlandy.com
on 22 Jun 2013 at 2:41