When I upload mp3 files to my DNN portal (04.07.00) initially they are entered into the DNN file database with a content type "audio/mpeg" which is correct. However some time later - I am guessing when DNN re-reads the directory to check that the files are still there - the content type of the file changes to application/octet-stream.

This causes a problem because I am adding these mp3 files to a podcast and the podcast module uses the content type from the files table meaning that I am sending out podcasts using the wrong content type.

Now not all of my mp3 files are being treated this way, although I think all of them in a particular directory are, so it might just be a case that the other directory hasn't been re-checked lately. My initial observation indicates that a couple of other file type were being handled incorrectly as well.

Can anyone offer any adice with regard to this? Is it a bug? Is it known? Is it something I'd doing wrong?

Cheers,

PS - apologies for the cross posting but this is quite urgent.

I have checked and mp3 is enabled - I am interested in how you think this could have any affect on what DNN does internally?

I think this is highly unlikely - when DNN scans the contents of the portal directory to update its list of files in the database I would expect the code to be reading the files directly from the file system - I'm not even sure you can access files via IIS from within code that is running internal to DNN.

AFAIK IIS will *only* be involved with the initial file upload - which is the time it gets the MIME type correct!

If I am wrong on this please give me an example of some server side code that access a file via IIS.

Thanks,