?

Log in

No account? Create an account

Previous Entry | Next Entry

...in Internet Explorer 7!

But perhaps that's redundant. "Dumb bugs" and "Internet Explorer" have long gone together like chocolate and peanut butter.

Anyway, one of my coworkers wanted to know why attempts to install Firefox always bombed out on her system. She was going to the Download page and clicking the "Run" button, which in reality actually means "download and then run."

The Firefox executable has spaces in its name (it's called something like "Install Firefox 3.0.6"). Now, as we all know, the Web turns spaces into %20, which is the hex ASCII code for a space.

So Explorer downloads the file as "Install%20%Firefox%20%3.0.6" but saves it as "Install Firefox 3.0.6". Here's where things go all hinkey:

It then runs the file "Install Firefox 3.0.6" but sets the path to the file as "Install%20Firefox%203.0.6"--which doesn't work. When the installer attempts to run, it can't locate its own built-in libraries because the Windows file path parsing APIs do not change "Install%20%Firefox%203.0.6" back into "Install Firefox 3.0.6".

*rolls eyes*

Tags:



Comments

valsmith
Feb. 6th, 2009 11:19 pm (UTC)
another
IE will parse a file and if it finds any code, it will attempt to execute it, regardless of the extension.

For example if you make a text (.txt) file and post it on a web server, Firefox will display the text as text, no matter what is in it. Firefox will only execute if the extension is correct (like .js)

If there is say a javascript or other code tag inside your text, IE will execute it, even if the file extension is .txt.

IIS, the sister to IE will do this as well. Ex. GIF files with embeded visual basic script.

Go mircosoft.

V.
tacit
Feb. 10th, 2009 12:09 am (UTC)
Re: another
*blink*

Dear. God.

I don't know WHAT to say to that, other than "OMFG what were they thinking??"