This content has been marked as final. Show 4 replies
If you change the value of the serverRequestCacheType setting in the oam-config.xml file (there is no UI way to do this) to FORM, then much of that data will be POSTed rather than seen in the URL. Please see Note 1281026.1 for more information about this setting.
That did indeed suppress all the unwanted information except now the log in page keeps recycling the https://company.org/oam/server/obrareq.cgi?encquery%3DeWIA0sgqkYSN2vVhSQb6h8eDlK1S6B5kmpAK25aAecYDpfUk0XAfP0qZeef%2FPIis1b2Sud1VHJ40Kl33Vu3J5zPgcq%2BmobsU9gzZyc8UICeqPLNtpyt6XgZxdgcGcuSPIW7Ziw8S5Nsnz%2FBvDAsw892LdoVW%2Bb0ibDasZ85OY1cn88I%2F0S%2B8bR0fQATq9y5MdSqUgtOwz8xDaixDj5tc07%2BfYwundBV2KgBqJQMdWYA8%2F6EbSUbsM406Zyxre%2B1UpcFquhHW%2BfdhWY%2FfsNq776BVcJK9WrnHeN54tjNomg1%2FUPIvS9TerPBFi4audinL0ifYrFHsuR%2FS9XUE6QyRPg%3D%3D%20agentid%3DWEBGATE%20ver%3D1
page over and over again until the browser throws a max header error.
I think changing that setting is correct but I think our custom log in pages are parsing the URL for the request_id and since even that is suppressed it keeps looping the OAM page looking for it over and over again but not getting it.