Troubleshooting the "Unable to decode" (IdP 3.3)

[O'Dowd, Josh]

> Probably the simplest thing to do first is see if their crawler 
> respects a web server's robots.txt.  You can google for plenty of 
> references of how to set that up, if you don't know already.  You can 
> block server paths and many other things with that.

>And the robot file needs to be on the SP server. It's hitting the IdP because the content on that side is protected and either shouldn't be, or needs to be blocked from indexing.

All good food for thought, much appreciated.

We are evaluating these and other options for our situation.

-Josh