← Back to team overview

launchpad-dev team mailing list archive

Breaking backward incompatibility with exception mapping

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

We have a bunch of exceptions that are mapped to 400 but should really
be mapped to 404. NoSuchPPA, NoSuchDistroSeries, NoSuchBranch, etc.

Fixing that is trivial, but we don't have a way of saying: if this
exception occurs when the webservice is using that service, use that
code, otherwise use that other code. We could probably add that
functionality, but is it worth it?

Changing this would break error handling logic that relied on catching
BadRequest to handle not found cases. Given that BadRequest is not
overly specific, it would make sense to confirm the error through the
string in that case, but I don't know if clients did this.

What do you think?

- -- 
Francis J. Lacoste
francis.lacoste@xxxxxxxxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk35LLsACgkQM2AFUiyz+TcMXACgqGBOyvQlmQ+Vd4gWWznPoeqE
oYsAoJV18BR/M+BXwO/z/ksN5V/lGIyF
=rkLg
-----END PGP SIGNATURE-----


Follow ups