Comment 2 for bug 2002525

Hi Jack,

I tried using a 3rd party API client to talk with MAAS API. This client has an OAuth signature assembly functionality; so, while filling out the required gaps (e.g oauth secrets), I accidentally emptied the "timestamp" field - which is mandatory. This resulted in a malformed OAuth signature string being generated, hence leading to the HTTP 500 being returned to the client.

Obviously, this won't happen if the signature is generated by some library (like oauthlib), so this is definitely a low-priority issue. However, I still don't think that unhandled HTTP500 is something that should be exposed to endpoint consumers.