Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.
 
  • Post
  • Reply
SirViver
Oct 22, 2008
Just a sidenote, I think a 400 Bad Request status code would be more appropriate for input validation errors than a 500 Internal Server Error.

Personally I'd only let the API's global unhandled exception handler return a 500. Any error condition you actively check for as part of your business rules should use whatever HTTP status code is most befitting of the situation - which is most likely one of the 400-range, like the ever elusive 418 I'm a teapot. But joking aside, realistically it's most likely a 400, 403, or 404.

Of course, technically it doesn't make a difference, as long as it's a status code that gets correctly interpreted as an error code by your HTTP client.

Adbot
ADBOT LOVES YOU

  • 1
  • 2
  • 3
  • 4
  • 5
  • Post
  • Reply