>Use the developer tools in the browser to see what is actually getting sent.
>
It actually helped to figure out the problem eventually. The http call was wrong from that page - not sure how it worked before. I made a fix and it's now working.