Using Access Manager v3.1.3-273 to proxy a Maximo application, mainly
for id injection, but also to SSL-ify it. Getting a strange behavior
from the rewrite rules define (really just one). Have one 'char' based
rule defined that changes 'http://<domain>.com' to
'https://<domain>.com' followed by the default 'word' rule. This works
fine in most places, but gives the following, mainly in the java applet
rewrites, but is showing up in some of the management screens:

--- before ---

<OBJECT
...

classid="java:com.ibm.ism.pmcom.webclient.topology .applet.TopologyApplet"

archive="http://<domain>.com/maximo/webclient/applets/flowmapapplet.jar,http://<domain>.com/maximo/webclient/applets/flowmap_applet_resources.jar,...

...

<PARAM NAME = "CODEBASE" VALUE=
"http://<domain>.com/maximo/webclient/applets" >
<PARAM NAME = "ARCHIVE" VALUE=
"http://<domain>.com/maximo/webclient/applets/flowmapapplet.jar,http://<domain>.com/maximo/webclient/applets/flowmap_applet_resources.jar,...

...


--- after ---

<OBJECT
...

classid="java:com.ibm.ism.pmcom.webclient.topology .applet.TopologyApplet"

archive="https://<domain>.com/maximo/webclient/applets/flowmapapplet.jar,http:/<domain>.com/maximo/webclient/applets/flowmap_applet_resources.jar,...

...

<PARAM NAME = "CODEBASE" VALUE=
"https://<domain>.com/https://<domain>.com/https://<domain>.com/https://<domain>.com/https://<domain>.com/https://<domain>.com/https://<domain>.com/https://<domain>.com/https://<domain>.com/maximo/webclient/applets"
>

<PARAM NAME = "ARCHIVE" VALUE=
"https://<domain>.com/maximo/webclient/applets/flowmapapplet.jar,https://<domain>.com/maximo/webclient/applets/flowmap_applet_resources.jar,...

...

Notice the one object archive attribute where the first .jar is fine,
but the following end up as 'http:/...' and the param/codebase value has
multiple 'https://<domain>.com' values prefixed on the line, though the
param/archive value looks fine. Has anyone else ran into this before?

We don't remember this with the previous version we were running on
(3.1.1), but we went through an upgrade on both the Maximo servers and
the LAGs at about the same time. The problems above only seem to happen
in the HTML emitted dynamically by Maximo due to browser sniffing (we
think) - i.e., the problem affects different attributes in IE than in
Firefox since the object html code is different in both.


--
slackmg
------------------------------------------------------------------------
slackmg's Profile: http://forums.novell.com/member.php?userid=65000
View this thread: http://forums.novell.com/showthread.php?t=448796