We just did a bit of debugging and the problem turned out to be that the wrong method was used (GET vs. POST) and this resulted in a 404. It might be a nice improvement if we returned 405 instead to give a better clue about the error.