On Mon, Mar 28, 2011 at 12:42 PM, Andrew Bennetts
<email address hidden> wrote:
> Judging from the OOPS report it's due to OOPSes OOPS-1910A1064, which
> means it's probably bug 520412. I don't know why it would be affecting
> us now and not before, but it appears that bug is well on the way to
> being fixed.
The fix is to just report a 400 class error to the client: the API
client is considered faulty in both cases.
On Mon, Mar 28, 2011 at 12:42 PM, Andrew Bennetts
<email address hidden> wrote:
> Judging from the OOPS report it's due to OOPSes OOPS-1910A1064, which
> means it's probably bug 520412. I don't know why it would be affecting
> us now and not before, but it appears that bug is well on the way to
> being fixed.
The fix is to just report a 400 class error to the client: the API
client is considered faulty in both cases.