Wrong filename when saving or attaching PDF files to email

[rudy]

Wrong filename when saving or attaching PDF files to email when viewed in web browser.

Description:
When viewing PDF documents in-browser where the URL is not a PDF filename (e.g. http://www.example.com/foo/document.aspx)

1) Saving the file with the browser plug-in saves it using the URL path as the filename (i.e. document.aspx.pdf).
This causes much confusion with our users who have the 'Hide extensions for known file types' option enabled in Windows 7 and only see the file as "document.aspx" in Windows Explorer.

2) Sending an email with the browser plug-in (Send by E-mail) attaches the PDF file with the URL path as the filename (i.e. document.aspx).
This causes problems with the recipients of the email not being able to open the PDF attachment due to the wrong filename extension.

Can both the above functions be fixed/modified to use the filename value in the Content-Disposition HTTP header instead of the URL when saving and attaching PDF files to emails?

Environment:
Windows 7
Internet Explorer 9
PDF XChange Viewer Version 2.5 (Build 201.0)

[Stefan - PDF-XChange]

Hello Rudy,

I am afraid that this could cause problems for users that do want to save files with the name with which they were uploaded on the server and when the link does include the file name, and has no Content-Disposition header.

After some consideration we have decided that we will not be adding this feature for now, however would like to do some further investigation. Could you please provide us with a sample link that we can test?

Best,
Stefan

[rudy]

Hi Stefan,

Can you at least save the PDF file without the URL extension? i.e. save as filename "document.pdf" instead of "document.aspx.pdf".

And attach the PDF file to the email as "document.pdf" instead of "document.aspx".

I'm afraid we do not have a sample link that is public. But you can easily recreate this scenario by writing a PDF file as binary a binary stream into the HTTP response and setting the appropriate HTTP Content-Type.

Thanks
Rudy

[Stefan - PDF-XChange]

Hello Rudy,

We discussed this further and we do believe that this is possible, but we will need a sample link to such a page so that we can run some tests and consider this for implementation.

Best,
Stefan

[rudy]

I've created the following webpage for you to test on.

http://www.jlta.com.au/PDF_XChange_Viewer.aspx

The 3 links on the page are:

1) Serves a PDF file from an ASPX webpage with the HTTP Content-Disposition filename value specified as "Content_Disposition_Filename.pdf"

2) Serves a PDF file from an ASPX webpage with no HTTP Content-Disposition filename value specified.

3) Links directly to the static PDF file.

Might I suggest that the PDF XChange Viewer plugin use the Content-Disposition filename value if it is available, and if it is not, use the URL but change any existing extension to ".pdf" (i.e. change xxx.aspx to xxx.pdf). If the URL is extension-less, just append ".pdf" to the filename (i.e. change xxx to xxx.pdf).

[Stefan - PDF-XChange]

Thanks for the samples Rudy,

I've created a ticket in our internal system:
#1455: Wrong filename when saving or attaching PDF files to email
So that this can be assigned to a developer and worked on.
Please do leave the samples on your server for some more time.

We will let you know when there are any news on this case.

Best
Stefan

[rudy]

Glad to hear that Stefan.

Is there an estimate on when this change will be available?

[Stefan - PDF-XChange]

Hi Rudy,

My colleague that will be working on it told me that he might even do it for the very next build - if time allows of course. So I would refrain from making any promises for now - but as soon as we have started working on it - we will update this forum topic.

Best,
Stefan

[Stefan - PDF-XChange]

Hello Rudy,

Just got a confirmation that this problem is fixed and the fix will be available in the next build.

Best,
Stefan