Definite improvement, thanks Ziv. We might consider returning 400s in these cases as well, but I've committed this patch in the meantime since it's not clear that malformed refresh values should really issue an error (or alternately, that they should yield refresh-friendly behavior).
http://codereview.appspot.com/207091/show
