I have a guide that is being served up in the workspace.
This guide works fine in all of the different browser versions provided they go through port 8080.
If however you enable SSL on your server (port 8443) and serve up the guide in the workspace, the end user can fill the entire form out only to have the browser identify the submit process as a Cross Site Scripting issue.
This is the result:
The data is essentially lost and guide disappears. I had a theory that maybe the submit process might be using the default server port for data submissions (8080) and created a customized submit process with the hardcoded targetURL.
I tried to test my theory and got the same result. I then modified my custom submit process to essentially do nothing (Started and ended the process with an abstract activity), and got the same result.
The only other thing that I could think of, is that the automatically generated action script classes might be hard coded to use default port instead of the SSL port.