API contact update with invalid vid should return a 404
EDIT: I was wrong, the API does send 404 if you send something that really looks like a vid. See below for details.
There was a time when the API returned a 404 with some tomcat HTML in it when we tried to update an inexisting contact via the update contact endpoint.
But now it returns an HTTP 200 OK when it didn't work.
When it works, it returns an HTTP 204 no-content.
I guess at least it's different but it is misleading as we can think it all worked well.
Just to check, are you explicitly including the Content Type: application/json header? I believe this is related to a known issue with the way requests missing this header get processed. I'm working with the team on a resolution to that issue, but in the interim I believe explicitly including that header should resolve the issue.
Yes, sending the header does not change the response.
BUT in my tests, I was using a non-integer value for the vid (the goal being to write a test case for the ruby gem).
If I send an integer of an inexisting contact, it works as expected.
Sorry for bothering you, I found the answer while writing a test case to answer your message