After upgrade, service sending with content-type: application/x-www-form-urlencoded no longer works.

[Rob Levy]

I upgraded my app and my service doesn't work anymore. If I go back to the older version, the service works fine.
My service is a content-type: application/x-www-form-urlencoded
If that is not passed as a header, then it gets an error back. I've checked to ensure that the header is being passed, however, it is still coming back with an error. Why is the service not working?

[Maryna Brodina]

Hello!

Please clarify what is the error you get?

[Rob Levy]

Hi Maryna,

There is no error. I have a Master page and when it loads I set the detail page to frmList.html.

I have a button that changes the detail page to frmEmail.html. On this page I put a button that says, "BACK" and when clicked, I set the detail page to frmList.html. However, this causes frmList.html to do a full reload and it takes too much time to load all the same content that I had loaded before.

Can I navigate from frmList.html--frmEmail.html (back to) frmList.html without reloading frmList.html?

Thank you,

Rob