Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-12-04 19:33:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Bug #54381 --> if we are loading an http url that ends in .dll and the server didn't

Browse Source 
give us a content type, then assume it is an unknown content type instead of
looking it up in the OS. This fixes the case were sites use ISAPI.dll and don't
specify content types.
r=gagan, sr=rpotts
This commit is contained in:
mscott%netscape.com 2000-10-11 22:54:19 +00:00
parent 1906e8a12d
commit e4420663eb
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
netwerk/protocol/http/src/nsHTTPChannel.cpp
View File

@ -402,8 +402,26 @@ nsHTTPChannel::GetContentType(char * *aContentType)
// No response yet... Try to determine the content-type based
// on the file extension of the URI...
//
// We had to do this same hack in 4.x. Sometimes, we run an http url that ends in special
// extensions like .dll, .exe, etc and the server doesn't provide a specific content type
// for the document. In actuality the document is really text/html (sometimes). For these cases,
// we don't want to ask the mime service for the content type
// because it will make incorrect conclusions based on the file extension. Instead, set the content type
// to unknown and allow our unknown content type decoder a chance to sniff the data stream and conclude
// a content type.
//
nsCOMPtr<nsIURL> url (do_QueryInterface(mURI));
PRBool performMimeServiceLookup = PR_TRUE;
if (url) {
nsXPIDLCString fileExt;
url->GetFileExtension(getter_Copies(fileExt));
if (fileExt && !nsCRT::strcasecmp(fileExt, "dll"))
performMimeServiceLookup = PR_FALSE;
}
nsCOMPtr<nsIMIMEService> MIMEService (do_GetService(NS_MIMESERVICE_CONTRACTID, &rv));
if (NS_SUCCEEDED(rv)) {
if (NS_SUCCEEDED(rv) && performMimeServiceLookup) {
rv = MIMEService->GetTypeFromURI(mURI, aContentType);
if (NS_SUCCEEDED(rv)) return rv;
// XXX we should probably set the content-type for this http response