Re: (ITS#7008) paged results against ldap-proxy errors with 'cookie is invalid'

[whm@stanford.edu]

This one just bit us again.  I know that the client should probably
not be using pr at all, but the client is an Google supplied
intergration application that we have little control over.  Is this
a problem that is going to be addressed as some point or will it
be treated as a known limitation?

Bill

-- 

"We have meet the enemy and he is us."
                                  Pogo