The code as it stands ALWAYS returns the serialized object in the response.  In addition, if the resource defines a `uri_prefix` it will ALSO return a 201 instead of 200 and a Location header.

In addition to returning the serialized object in both cases, you could return 201 in both cases as well.  But I'm not sure it makes sense to return the Location header in both cases.  Werkzeug expects the Location header to be a URI.  So unless you are prepared to return a reachable URI (something you could actually GET), I'd leave it out unless you have a `uri_prefix`.

I hope that clarifies things.