Hi Napernik,
Unfortunately I am unable to send you a copy of the site as it stands, but I will try and recreate the issue on a vanilla composite instance.
I don't think I am suffering the same porting issue. It seems to be posting to this url:
http://sub.mysite.com/Composite/content/flow/FlowUi.aspx?consoleId=key9364657565042436&flowHandle=_flowTokenType_%3d%27Composite%5c.C1Console%5c.Workflow%5c.WorkflowFlowToken%2cComposite%27_flowToken_%3d%274cf26f60-b794-493a-b364-1df5021e053c%27&elementProvider=PageElementProvider
Which then produces the following 404:
HTTP/1.1 404 Not Found
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Mon, 03 Jun 2013 14:19:25 GMT
Content-Length: 5755
<!DOCTYPE html>
<html>
Composite.Core.WebClient.Renderings.RenderingContext.InitializeFromHttpContextInternal() +1059
Renderers_Page.OnPreInit(EventArgs e) +36
System.Web.UI.Page.PerformPreInit() +49
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1844
</pre></code>
<!-- [HttpException]: Page not found - either this page has not been published yet or it has been deleted. at Composite.Core.WebClient.Renderings.RenderingContext.InitializeFromHttpContextInternal() at Renderers_Page.OnPreInit(EventArgs e) at System.Web.UI.Page.PerformPreInit() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) [HttpUnhandledException]: Exception of type 'System.Web.HttpUnhandledException' was thrown. at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --><!-- This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.--> Again, if I log in as a different user though the issue does not appear. Very strange.
I appreciate this is very hard for you to debug without being able to reproduce it. I will try later to get something together for you guys.
Unfortunately I am unable to send you a copy of the site as it stands, but I will try and recreate the issue on a vanilla composite instance.
I don't think I am suffering the same porting issue. It seems to be posting to this url:
http://sub.mysite.com/Composite/content/flow/FlowUi.aspx?consoleId=key9364657565042436&flowHandle=_flowTokenType_%3d%27Composite%5c.C1Console%5c.Workflow%5c.WorkflowFlowToken%2cComposite%27_flowToken_%3d%274cf26f60-b794-493a-b364-1df5021e053c%27&elementProvider=PageElementProvider
Which then produces the following 404:
HTTP/1.1 404 Not Found
Cache-Control: private
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Mon, 03 Jun 2013 14:19:25 GMT
Content-Length: 5755
<!DOCTYPE html>
<html>
<head>
<title>Page not found - either this page has not been published yet or it has been deleted.</title>
<meta name="viewport" content="width=device-width" />
<style>
body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;}
p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px}
b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px}
H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red }
H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon }
pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt}
.marker {font-weight: bold; color: black;text-decoration: none;}
.version {color: gray;}
.error {margin-bottom: 10px;}
.expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
@media screen and (max-width: 639px) {
pre { width: 440px; overflow: auto; white-space: pre-wrap; word-wrap: break-word; }
}
@media screen and (max-width: 479px) {
pre { width: 280px; }
}
</style>
</head>
<body bgcolor="white">
<span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1>
<h2> <i>Page not found - either this page has not been published yet or it has been deleted.</i> </h2></span>
<font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">
<b> Description: </b>An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
<br><br>
<b> Exception Details: </b>System.Web.HttpException: Page not found - either this page has not been published yet or it has been deleted.<br><br>
<b>Source Error:</b> <br><br>
<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code>
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:<br><br>1. Add a "Debug=true" directive at the top of the file that generated the error. Example:<br><br> <%@ Page Language="C#" Debug="true" %><br><br>or:<br><br>2) Add the following section to the configuration file of your application:<br><br><configuration><br> <system.web><br> <compilation debug="true"/><br> </system.web><br></configuration><br><br> Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.<br><br>Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.</code></td>
</tr>
</table>
<br>
<b>Stack Trace:</b> <br><br>
<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code><pre>
[HttpException (0x80004005): Page not found - either this page has not been published yet or it has been deleted.]Composite.Core.WebClient.Renderings.RenderingContext.InitializeFromHttpContextInternal() +1059
Renderers_Page.OnPreInit(EventArgs e) +36
System.Web.UI.Page.PerformPreInit() +49
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1844
</pre></code>
</td>
</tr>
</table>
<br>
<hr width=100% size=1 color=silver>
<b>Version Information:</b> Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18044
</font>
</body>
</html><!-- [HttpException]: Page not found - either this page has not been published yet or it has been deleted. at Composite.Core.WebClient.Renderings.RenderingContext.InitializeFromHttpContextInternal() at Renderers_Page.OnPreInit(EventArgs e) at System.Web.UI.Page.PerformPreInit() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) [HttpUnhandledException]: Exception of type 'System.Web.HttpUnhandledException' was thrown. at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --><!-- This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.--> Again, if I log in as a different user though the issue does not appear. Very strange.
I appreciate this is very hard for you to debug without being able to reproduce it. I will try later to get something together for you guys.