views:

107

answers:

2

it seems IIS6 on Win2003 R2 Enterprise x64 SP2 will not allow you to use .com in a url path.

e.g if i create a folder foo.com in my web root, containing a default.htm, this url results in a 404:

http://localhost/foo.com/default.htm

however, following the exact same steps on Win2003 R2 Standard x86 SP2, and IIS6 will serve up the file just fine.

Neither server has urlscan installed.

Is there a way to tell IIS6 on Win2003 x64 to allow .com in a url path?

+1  A: 
spender
thanks for the quick reply. i dont believe im experiencing that issue as my x64 box is returning HTTP 404 not HTTP 400. What's really baffling me is that it works on x86 but not x64 :-(
shockstump
+1  A: 

ok problem solved. this post, whilst not directly giving the answer, gave me enough of a clue:

David Wang's blog

Basically, my x64 IIS site had it's execute permissions configured "Scripts AND executables" whereas my X86 IIS site was configured "Scripts Only"

So it seems that, even though .com was only appearing in the path of my url, IIS was treating it as an executable file, for which it has no application mapping hence the HTTP 404

shockstump