Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryMIME issue workarounds anyone?MIME issue workarounds anyone?
Previous
 
Next
New Post
11/2/2005 4:13 PM
 
Hi all,

I'm working on my first install of the Repository module and I've run into a problem with mime types for the documents. I know that this may be "old hat" because I can find a few references to this issue with GDR and other DNN modules, however, I have not found any solutions posted.

The repository that I'm setting up will store PDF docs and be serving a mixed set of IE and Firefox users.  The PDFs download OK for the IE users, but, not the Firefox users.  Under Firefox, we get that the document is sometimes a HTM (ascii) doc and sometimes a ZIP (binary) doc.  This looks to me like a mime type issue.  I can download a PDF from the server using a direct URL and get it fine in both browsers, so I don't think it's a server issue.  Is there someway I can jiggle the DNN or Repository settings to get this to work?  My user community is not very tech savvy and I don't look forward to reminding them 10 times a day how to download a document (and agree with them that yes it used to be better with the old system

Thanks for tips & pointers,

Greg Croasdill
http://www.glaa-alpacas.org (see About/Newsletters for example)


 
New Post
11/3/2005 10:57 AM
 

Greg,
I may be mistaken but I don't think it's anything that you will be able to fix on the server. I believe it's a FireFox issue that's well documented ( search for 'FireFox PDF download' in Google )

If you have users who are using FireFox, the fix appears to be the download and install of an extension called 'PDF Download'. You can check the FireFox extensions page for details.

 
New Post
11/3/2005 11:04 AM
 
 
New Post
11/3/2005 5:46 PM
 
Thanks for the reply, but...  my point is that (as a heavy FireFox user) I've never had to use a plugin to make PDFs show up.  This site, on the same server, using plain old HTML pages used to work this way. I've tested downloading the PDF docs uploaded via the Repository and they show up fine in the browsers ->IF<- you navigate directly to them (e.g. go to - http://www.glaa-alpaca.org/portals/0/Repository/GLAAnews9-02.e4eb5a1c-fb6a-4fbf-b3d5-c136ce6d14f7.pdf ). 

So... what's the diff between using the repository's link and navigating directly? At a guess, I think this has something to do with the postback/download function. Is there a way to have the repository just produce a link to the file without using a postback? It's my belief that the PDF docs (and other office docs like word, ppt, etc) are not shown in the context of a DDN template, so you should just have a link to the document?

Thanks, I may be ranting a bit, but I do appreciate your work!

GregC

 
New Post
11/7/2005 6:49 AM
 

The reason that the Repository module uses a postback to inititiate a download instead of simply injecting a direct link to the file when it renders is so that downloads can be tracked. If I just inject a link to the file, there's no way to know how many times a file has been downloaded.

Also, When the postback fires, the download count is incremented and the file is streamed to the browser. This supports very large files ( hundreds of MB ). Again, a simple link would fail ( the asp.net process would timeout ) for files that could possibly be as large as a Gig.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositoryMIME issue workarounds anyone?MIME issue workarounds anyone?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out