IIS 6.0 Handle dots / periods in URL other than prior to extension?

IIS 6.0, not using URLScan. URLs that point to documents that contain dots / periods in their filename fail to load. The same document minus the extra dots / periods, except for the one before the extension, work fine.

I've searched everywhere and not found a solution. URLScan has an option to toggle this, but IIS 6.0 doesn't need it. Plus, I've heard even installing URLScan over IIS 6.0 and enabling dots does NOT help.

IIS is setup to allow Parent Paths.

I've searched the registry and metabase for an appropriate setting to flip. No luck.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mcouillardAuthor Commented:
Example of a URL that comes up "not found" despite the exact file existing:

Example of a URL that works fine:

I suspect this is related to IIS 6s new method of handling MimeTypes. XLS is a supported MimeType, but the extra dots seem to make IIS think the file isn't an XLS.

I don't think that it is IIS doing this since I cannot repeat the problem on my own IIS 6 platform.

What is the error message received when you try to access those scripts?

mcouillardAuthor Commented:
Good thought, meverest! Unfortunately I removed the only possibly offending line in my ISAPI REWRITE configuration and it failed to make a difference.

The exact error in Firefox is "Page Load Error" followed by "File not found". IE attempts to load the file but it's always 187 bytes and ends up being an error message.

Here's another, more real-life example of the URL that fails with extra dots:

(Yes, I've tried both with and without SSL - same result)

are you sure that it isn't the whitespaces causing the problem?  What does the web site log reckon the missing file is?

mcouillardAuthor Commented:
Turns out it was faulty character encoding. An ASP function fixed the URL enough to make it workable in a browser.

Function URLFileNameFix2(str)
        URLHolder =(Server.URLEncode(TRIM(str)))
      URLHolder = Replace(URLHolder,"%2F", "/")
      URLHolder = Replace(UrlHolder,"+", "%20")
      URlHolder = Replace(URLHolder,"%2E",".")
      URLHolder = Replace(UrlHolder,"%5C","\")
      URLHolder = Replace(URLHolder,"%5F","_")
      URLHolder = Replace(URLHolder,"%5B","[")
      URLHolder = Replace(URLHolder,"%5D","]")
      URLHolder = Replace(URLHolder,"%3F","?")
      URLHolder = Replace(URLHolder,"%3D","=")
      URLHolder = Replace(URLHolder,"%2D","-")
      URLHolder = Replace(URLHolder,"%20"," ")
      URLFileNameFix2 = URLHolder
end Function

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.