Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Natao arisiva ity resaka mitohy ity. Mametraha fanontaniana azafady raha mila fanampiana.

MIME Type for .zip file

  • 2 valiny
  • 3 manana an'ity olana ity
  • 1 view
  • Valiny farany nomen'i manstis

manstis
manstis
more options

Hello,

I am developing a web application and notice the MIME-type for .zip files is "application/x-sdlc" mapped in mimeTypes.rdf.

My question, why is this so?

The common MIME-types for ZIP files is normally one of: "application/zip", "application/x-compress", "application/x-compressed", "application/x-zip", "application/x-zip-compressed", "application/zip-compressed" or "application/x-7zip-compressed".

I can code around the problem, but I am just curious.

Thanks,

Mike

Hello, I am developing a web application and notice the MIME-type for .zip files is "application/x-sdlc" mapped in mimeTypes.rdf. My question, why is this so? The common MIME-types for ZIP files is normally one of: "application/zip", "application/x-compress", "application/x-compressed", "application/x-zip", "application/x-zip-compressed", "application/zip-compressed" or "application/x-7zip-compressed". I can code around the problem, but I am just curious. Thanks, Mike

All Replies (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Maybe you once have set an automatic action for a ZIP file and that file was send with the MIME type "application/x-sdlc". You can try to remove that line from mimeTypes.rdf to see if that makes it work better.

manstis
manstis Tompon'ny fanontaniana
more options

AFAIK mimeTypes.rdf is the standard vanilla Fire Fox MIME mapping file following a fresh install (3.6.18); so nothing custom here I am afraid. However a colleague with FF5 says the problem no longer exists - I am to try that.