Feb 23 at 10:23 PM
Edited Feb 23 at 11:19 PM
Our V5.0 (also starting with 5.6) has been working wonderfully with an implementation of MVCFunctions. After upgrading a test site to V6.0 I noticed the MVC Functions don't seem be working the same.
An example is a MVCFunction that is handling a form rendering in a page and post back. When I do a view source, the action URL that is resulting from the rendering is very different and the post back fails.
<form id="loginForm" action="https://www.mydomain.com/Login" class="form-horizontal" method="post" novalidate="novalidate">
After the upgrade to V6.0
<form id="loginForm" action="https://www.mydomain.com/Composite/api/Router?action=Login&controller=Secure" class="form-horizontal" method="post" novalidate="novalidate">
When doing the form post in V6 will just result in a blank page. Can you think of why the action URL was expanded to include a "/Composite/api/Router" as part of the path?