Problem

URL Searches are not running correctly if a search string starts with a pound-sign (#) character.

Solution

The Internet specifications for passing URLs say that a pound sign character must be encoded when passed via a URL. 
 
Passing the value of:  %23 instead of # is the equivalent of encoding the # character and should fix the problem. (The %23 character combination passes the ASCII character value for the pound sign instead of the actual character into the URL.)
 
For example:
  • URL that will NOT pass the pound sign correctly:
    http://125.1.1.53:443/IMAGESERVER/DOC100R?ACTION=Search&ISESSION=TEST082...
  • URL that will pass the pound sign correctly:
    http://125.1.1.53:443/IMAGESERVER/DOC100R?ACTION=Search&ISESSION=TEST082...
 

Still have questions? We can help. Submit a case to Technical Support.

Last Modified On: December 10, 2016