LocationMap fails to find files with embedded spaces in the URL

• Key: FOR-736
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Ross Gardler
• Reporter: Greg Jenci
• Component/s: Locationmap
• Affects Version/s: 0.8
• Fix Version/s: 0.8

Description

The LocationMap fails to find files that have spaces embedded in the URL. For instance, in my case, it will find

http://10.222.12.456/open/System%20Identification%20Report.pdf

But fails to find it as

http://10.222.12.456/open/System Identification Report.pdf

Incidentally, for information on resolving to PDF files please see http://www.mail-archive.com/[e-mail]/msg01212.html

Comments

[Tim Williams]

Can someone explain a bit more about this? Spaces that aren't URI encoded aren't a valid URL, right? So why should it worry about them? Maybe I'm missing the issue...

[Ross Gardler]

My own thinking is that it is a convenience if we allow people ot enter the URL without the URL encoding. It is much easier to type a space than %20

The same would go for other characters that need encoding. It's simply a case of passing the value through a utility method before returning it as a lcoation isn't it?

[Ross Gardler]

http: urls are now URL Encoded before being returned. This should solve the problem, do we need to add any other protocols to the URL encoded list?