Troubleshooting the "Unable to decode" (IdP 3.3)

Cantor, Scott cantor.2 at osu.edu
Thu Aug 31 16:13:39 EDT 2017


> 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.

-- Scott



More information about the users mailing list