[AndrewD]

Originally Posted by kompakt

As you mentioned, this is the way the links are parsed in the final 2.2.6 release.

This is still giving me problems in Firefox and users end up getting an html page if I have the hit-parade set to 0. My host does not add custom mime types, they are not known by the server and are defined on my .htaccess file. I have to keep the hit parade set to 1 for this to work since the location of the files is revealed, the browser picks up the correct mime-type from my .htacess file.

Is it possible to add them somehow into the mime-types in the local_links.php?

I'm a little confused - sorry. First, I assume you mean the setting "force_redirect", not "hit_parade".

When force_redirect is set to 0, LDM behaves as follows:

- if the file type exists in the VBulletin attachment table, then the mimetype data set up in that table is used.
- otherwise, LDM issues a simple browser redirect.

So you should create new entries in VBulletin attachments table for each of the filetypes you want to deal with. The .htaccess mimetype data only comes into play when this is not available.

Now, there is a another problem with Firefox: When you do a "right click/save link as", Firefox does not 'pre-fetch' any information before processing the 'save as' command. As a result, you end up downloading a "scriptname.php" file containing html, rather than (e.g.) the correctly named mp3 file. This has been long discussed on the Firefox development forum - it's a deliberate design choice on their part to speed up processing. It's one area where IE does (in my opinion) a better job.

Am I missing something?