iis is configure to handle http request and pass requests to domino with websphere iisWASPlugin_http.dll version 5.
Everything is ok for normal urls.
But if in the url name you have a space car the space car is replace by %20 chain, the new chain is sent to iisWASPlugin_http.dll and converted to a space car.
In this case Websphere could not send the result to IIS.
If you go to domino HTTP port with the same URL everything is Ok.
Two questions :
First Is it a fix avalaible to correct the problem ?
Second Is it a tool to test all pages and links to help admin to rename attached files and other ressources
more informations from websphere logfile[Wed Dec 31 16:24:30 2003] 000003e4 0000014c - TRACE: lib_util: decodeURI: Decoding ‘/intranet/base.nsf/Images/Name%20With7%20Space%20car/$file/Name%20with%20Space%20car.JPG’
[Wed Dec 31 16:24:30 2003] 000003e4 0000014c - TRACE: lib_util: decodeURI: Decoded to ‘/intranet/base.nsf/Images/Name With Space car/$file/Name With Space car.JPG’
[Wed Dec 31 16:24:30 2003] 000003e4 0000014c - TRACE: ws_common: websphereShouldHandleRequest: trying to match a route for: vhost=‘hostname’; uri=‘/intranet/base.nsf/Images/Name With Space car/$file/Name With Space car.JPG’
[Wed Dec 31 16:45:06 2003] 000007ac 00000698 - TRACE: ws_common: websphereUriMatch: Comparing ‘.nsf’ to ‘/intranet/base.nsf/Images/Name With Space car/$file/Name With Space car.JPG’ in UriGroup: default_host_URIs score is 4
However, it seems to be possible to work around it by replacing “%20” with a “+”. Optionally, as you say, by reprogramming the application(s) in question to not contain any spaces.
As far as I know this was not a problem when using WAS 4.0x, with the same specs as listed above.
Not sure whether or not this is some sort of IIS problem or WAS 5.0.0.0 problem, or perhaps a combination. It seems to work fine when accessnig the Domino HTTP stack directly.
Will you please let me know if you come up with a solution other than reprogramming or by editing the URL? I will do the same. Perhaps some sort of settings on how to interpret spaces or somehting like that available in the IIS or WAS config…?
When reverting to the V4 plugin you need to update the registry with a new key, and some new string values as well. This is all documented quite well in the 6.0.3 release notes. Note that you need to specify 5.0.0.0 in the registry key instead of 5.0 as described in the release notes for 6.0.3.
I think the same XML file will work fine, at least it works without modifications when upgrading from V4 to V5. According to the documentation you also need to create some new directories with corresponding registry settings.
Finally, in contrast to the V5 plugin, the V4 plugin consists of two files. The plugin, and a common dll of some sort. It’s all in the release notes.