Invalid URL in code after upgrading from Domino 7 to 9.0.1

After coping one of our database from a Domino 7 server onto a new 9.0.1 server it is causing HTTP Web Server: Invalid URL Exception errors.

The Database used Ajax calls to get data form other databases and display it on a page.

The problem seems to be caused by the # character in the URL being encoded as %23 (# is used as a seperator between values for a combined category)

I have tried entering the url directly in a browser and

http://10.110.3.21/IEDB/KSAMAOS.nsf/pendingactionstasks?OpenView&RestrictToCategory=Mike%20King%23STAAssigned&Count=10 http://10.110.3.21/IEDB/KSAMAOS.nsf/pendingactionstasks?OpenView&RestrictToCategory=Mike%20King%23STAAssigned&Count=10 is giving the error

http://10.110.3.21/IEDB/KSAMAOS.nsf/pendingactionstasks?OpenView&RestrictToCategory=Mike%20King#STAAssigned&Count=10 http://10.110.3.21/IEDB/KSAMAOS.nsf/pendingactionstasks?OpenView&RestrictToCategory=Mike%20King#STAAssigned&Count=10 is opening up OK

I have tried to force the url to use the # value but when posted via the Ajax command it is converted back to %23

Does anyone know why %23 is now seen as invalid in Domino 9 and is there anyway around it or do I have to use a different seperator in my views now?

Subject: Thoughts…

I haven’t debugged this, but my best guess seeing you moving from 7 to 9 is that an XSS issue likely caused this. The ‘#’ character is reserved in the URL as an anchor and I think that is why you’re seeing this new behavior. My thinking is that you’d be best served by sticking to a non-reserved character for the delimiter.