Hi,
When I click an attachment if any kind (PDF, JPG, DOC, etc.) The binary code of the attachment is shown rather than the real contant. Also, If I choose to download the file it is saved as download.htm instead of the real file name? Any ideas why this would happen?
I am using the SVN version 495 of RoundCube.
Best regards,
Jes Kasper Klittum
enavn ApS [ Administration ] Ringstedgade 11 A 4700 Næstved
enavn ApS [ Datacenter ] Århusgade 88 2100 København Ø
Tel.: +45 88205000 Fax: +45 88205010 support@enavn.dk
Jes Kasper Klittum wrote:
Hi,
When I click an attachment if any kind (PDF, JPG, DOC, etc.) The binary code of the attachment is shown rather than the real contant. Also, If I choose to download the file it is saved as download.htm instead of the real file name? Any ideas why this would happen?
Please analyze the HTTP headers and check the value set for Content-Type. This will be set to content-type specified for the attachment within the message. Test with different mails and different browsers.
Search the mail source for 'Content-Type:'. If this is not set, we should probably create a fallback to a default type (e.g. application/octet-stream)
I am using the SVN version 495 of RoundCube.
Please test with the latest SVN version (currently 558).
~Thomas
Hi Thomas,
Thomas Bruederli skrev:
Please analyze the HTTP headers and check the value set for Content-Type. This will be set to content-type specified for the attachment within the message. Test with different mails and different browsers.
When I click the attachment, and then right-click and select "View source" and search for content-type, then I get:
<meta http-equiv="content-type" content="text/html; charset=UTF-8" /> > > Search the mail source for 'Content-Type:'. If this is not set, we should > probably create a fallback to a default type (e.g. application/octet-stream)
The Mail content type is: Content-Type: application/pdf
Please test with the latest SVN version (currently 558).
We have had major issues with 495, so we are not very keen on changning to a SVN version that is not working "without major issues" as your say.
Jes
Jes Kasper Klittum wrote:
Please test with the latest SVN version (currently 558).
We have had major issues with 495, so we are not very keen on changning to a SVN version that is not working "without major issues" as your say.
I don't mean that you should work with a SVN version but I'd like you to verify the bugs with the latest development version before posting them here or opening tickets for them. Could be that they're fixed in the meantime or that your current version (which is a SVN checkout, right?) has some temporary issues.
~Thomas
-
Jes Kasper Klittum -
Thomas Bruederli