>>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
Getting a 400 from the WebAPI controller was a good indication of that :-}
- not sure how it worked before. I made a fix and it's now working.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only