see issue #204
When is this possible?
Certain users could request for a reset password url (the resulting url was customized via config) and the resulting URL could cause the server to return a 503 due to TypeError exception being bubbled up from itsdangerous.
since the patch I now get a proper 200 with error message instead of the trace. I was able to reproduce the error on safari, chrome and ie9.
Could you please write a test case for your situation?
I will look into producing the test case (it's basically a mangled urlencode string)
@mattupstate I produced the test, fails because python 3.3
catch possible TypeError and ValueError from serializer
add test to show TypeError can occur
update to make test run red