Issue 3859: Investigate extension matching, instead of content sniffing,
for FTP resources
http://code.google.com/p/chromium/issues/detail?id=3859
Comment #5 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Status: Available
Owner: ---
Issue 3859: Investigate extension matching, instead of content sniffing,
for FTP resources
http://code.google.com/p/chromium/issues/detail?id=3859
Comment #3 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Cc: [EMAIL PROTECTED]
--
You receive
Issue 3859: Investigate extension matching, instead of content sniffing,
for FTP resources
http://code.google.com/p/chromium/issues/detail?id=3859
Comment #2 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Type-Bug -Type-Bug -Area-Misc
Issue 3859: Investigate extension matching, instead of content sniffing,
for FTP resources
http://code.google.com/p/chromium/issues/detail?id=3859
Comment #1 by [EMAIL PROTECTED]:
Do we have a way to investigate the compat impact? One thing we could do
is add a histogram in the
mime_sniffer
Issue 3859: Investigate extension matching, instead of content sniffing,
for FTP resources
http://code.google.com/p/chromium/issues/detail?id=3859
New issue report by lcamtuf:
When receiving a file over FTP, Chrome currently treats it the same as a
case of a HTTP resource received with no Conte
