Setting expiry too far into the future creates issues

If you set it 30, 40, 50 years ahead, not a problem. The document comes back with the expected expiry. However, try setting to 87 years from now, it fails to add the doc. Yet, 86 years from now works. If you get excited and try 200 years from now (2219), it ends up setting it for 2083. So of course it is just rolling over...

Clearly the time is represented differently on the server (not a long, probably unsigned int). I think our great grandchildren will notice this and be sad. We can prevent this by maybe verifying the representation on the server, and raising an exception without sending this off if the expiry exceed this value.

I doubt this is super high priority, but best to note it just in case we are in there for other things...