tag:blogger.com,1999:blog-23714519.post561784177162602424..comments2023-10-18T02:14:08.061+11:00Comments on Alex's Corner: HTTP Range & Request-Range Request Headerskuza55http://www.blogger.com/profile/03932544559060480887noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-23714519.post-23071362747534755032008-07-23T21:55:00.000+10:002008-07-23T21:55:00.000+10:00I can't reproduce this bug in 6.0.2900.2180.xpsp_s...I can't reproduce this bug in 6.0.2900.2180.xpsp_sp2_gdr - it might be fixed. Finally. :)<BR/><BR/>Best,<BR/><BR/>Andr3wAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-23714519.post-36274905878621694182008-07-23T21:22:00.000+10:002008-07-23T21:22:00.000+10:00Just a reply to FindMimeFromData():http://msdn.mic...Just a reply to FindMimeFromData():<BR/>http://msdn.microsoft.com/en-us/library/ms775147.aspx<BR/><BR/><BR/>The function will return the server content-type header if it doesn't recognize it. So the server might use the header "image/leave-me-alone" instead of "image/gif" and IE wouldn't change try to guess it. <BR/><BR/>Then, because it fails to find it, it will look at the extension - and (probably) correctly use image/gif. <BR/><BR/>I haven't tested it, but this is how I understand the documentation. It is an ugly hack anyway, but better this than checking first 256 bytes or copying the image... <BR/><BR/>Anyway, just an idea, thought I would share. :)<BR/><BR/>Nice blog!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-23714519.post-73809453089333577932008-02-29T15:27:00.000+11:002008-02-29T15:27:00.000+11:00Nice!Nice!Script Hackerhttps://www.blogger.com/profile/15223820577941348147noreply@blogger.com