|
Home > Archive > IIS Server > September 2005 > Mime Types in IIS 6.0
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Mime Types in IIS 6.0
|
|
|
| I though that if there wasn't a MINE type specified Globaly or locally in
the ISM the user would get a 404.3. I can't get this to work with .mpg
files.
I remove the Mime type and the user gets a dialog box to either save or open
the file, along with a 200 code in the logs.
I recyled the App Pool and WWW Service just in case. It's still not working,
Anybody know what's happening here?
Does this have something to do with the user IE settings?
Thanks
| |
| David Wang [Msft] 2005-09-19, 2:49 am |
| The effective MIME Type is a merge of Content-Type from the system Registry,
global MIME Map, and per-URL MIME Map.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"noone" <noone@nowhere.com> wrote in message
news:%23bqBoqEvFHA.3740@TK2MSFTNGP14.phx.gbl...
I though that if there wasn't a MINE type specified Globaly or locally in
the ISM the user would get a 404.3. I can't get this to work with .mpg
files.
I remove the Mime type and the user gets a dialog box to either save or open
the file, along with a 200 code in the logs.
I recyled the App Pool and WWW Service just in case. It's still not working,
Anybody know what's happening here?
Does this have something to do with the user IE settings?
Thanks
| |
|
| Hi Dave,
Thanks for responding.
Are all these on the server? If yes, then isn't the Metabase basially the
same as the Registry on the server.
Is the URL MIME map on the client's end.
My apologies for not understanding the entire answer.
Thanks
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:OhiVzdMvFHA.720@TK2MSFTNGP15.phx.gbl...
> The effective MIME Type is a merge of Content-Type from the system
> Registry,
> global MIME Map, and per-URL MIME Map.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "noone" <noone@nowhere.com> wrote in message
> news:%23bqBoqEvFHA.3740@TK2MSFTNGP14.phx.gbl...
> I though that if there wasn't a MINE type specified Globaly or locally in
> the ISM the user would get a 404.3. I can't get this to work with .mpg
> files.
> I remove the Mime type and the user gets a dialog box to either save or
> open
> the file, along with a 200 code in the logs.
> I recyled the App Pool and WWW Service just in case. It's still not
> working,
> Anybody know what's happening here?
> Does this have something to do with the user IE settings?
> Thanks
>
>
>
| |
| David Wang [Msft] 2005-09-19, 6:02 pm |
| Everything I said is on the server-side.
IIS Metabase and Windows Registry are totally different things and are
completely different data stores.
I have no idea what you mean by "URL MIME map on the client's end"...
Right now, it sounds like you have a MIME Type for .mpg configured in one or
more of the three locations I mentioned (per URL MIME Map [I think you
referred to it as "locally specified MIME Map"], global MIME Map, and
Registry), and until you remove the configuration from all three, you will
never get a 404.3 from the IIS Static File Handler. On a default system, I
see .mpg defined both in the Windows Registry and global MIME Map in the
metabase, and neither are configurable via the IIS Manager UI.
Please read my blog entries for more understandings on how IIS request
processing works:
http://blogs.msdn.com/david.wang/ar...s_on_IIS_6.aspx
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"noone" <noone@nowhere.com> wrote in message
news:e5aYpdQvFHA.2504@tk2msftngp13.phx.gbl...
Hi Dave,
Thanks for responding.
Are all these on the server? If yes, then isn't the Metabase basially the
same as the Registry on the server.
Is the URL MIME map on the client's end.
My apologies for not understanding the entire answer.
Thanks
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:OhiVzdMvFHA.720@TK2MSFTNGP15.phx.gbl...
> The effective MIME Type is a merge of Content-Type from the system
> Registry,
> global MIME Map, and per-URL MIME Map.
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "noone" <noone@nowhere.com> wrote in message
> news:%23bqBoqEvFHA.3740@TK2MSFTNGP14.phx.gbl...
> I though that if there wasn't a MINE type specified Globaly or locally in
> the ISM the user would get a 404.3. I can't get this to work with .mpg
> files.
> I remove the Mime type and the user gets a dialog box to either save or
> open
> the file, along with a 200 code in the logs.
> I recyled the App Pool and WWW Service just in case. It's still not
> working,
> Anybody know what's happening here?
> Does this have something to do with the user IE settings?
> Thanks
>
>
>
| |
|
| Thanks.... I got it to work perfectly.
I removed it from the registry and ISM to delete it from the IIS, then I
added it to seperate webs or directories bleow web sites.
Thanks for your response, it helped me.
"David Wang [Msft]" <someone@online.microsoft.com> wrote in message
news:%23l05DaVvFHA.2504@TK2MSFTNGP15.phx.gbl...
> Everything I said is on the server-side.
>
> IIS Metabase and Windows Registry are totally different things and are
> completely different data stores.
>
> I have no idea what you mean by "URL MIME map on the client's end"...
>
> Right now, it sounds like you have a MIME Type for .mpg configured in one
> or
> more of the three locations I mentioned (per URL MIME Map [I think you
> referred to it as "locally specified MIME Map"], global MIME Map, and
> Registry), and until you remove the configuration from all three, you will
> never get a 404.3 from the IIS Static File Handler. On a default system, I
> see .mpg defined both in the Windows Registry and global MIME Map in the
> metabase, and neither are configurable via the IIS Manager UI.
>
> Please read my blog entries for more understandings on how IIS request
> processing works:
> http://blogs.msdn.com/david.wang/ar...s_on_IIS_6.aspx
>
> --
> //David
> IIS
> http://blogs.msdn.com/David.Wang
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> //
> "noone" <noone@nowhere.com> wrote in message
> news:e5aYpdQvFHA.2504@tk2msftngp13.phx.gbl...
> Hi Dave,
> Thanks for responding.
> Are all these on the server? If yes, then isn't the Metabase basially the
> same as the Registry on the server.
> Is the URL MIME map on the client's end.
> My apologies for not understanding the entire answer.
> Thanks
>
>
>
> "David Wang [Msft]" <someone@online.microsoft.com> wrote in message
> news:OhiVzdMvFHA.720@TK2MSFTNGP15.phx.gbl...
>
>
>
|
|
|
|
|