>Use the developer tools in the browser to see what is actually getting sent.
>

No, even after we fix what we assumed to be a problem, it didn't help. For now I deferred this problem to my colleague - he seems to be better in figuring this out and tracing angularjs code (which I really don't want to).