At the moment the issue is still unresolved. As it not affect any operation we ignore it, but it is still pending a resolution.  

Answer my own question. We use an IIS URL rewrite between the internet and Author. We found that IIS is the one updating the URL. Not AEM. Tested this by calling the server directly instead of using IIS URL Rewrite.

I have a simple servlet that upload a PDF to adobe esign and I manage to get a URL back.  I now want to redirect the client to this URL. The actual URL is valid if I copy-paste it into a browser, but the AEM override the below URL from https://secure.na1.echosign.com/.....to https://my.aem.server.ur...

Alternative we were thinking to override the default 401-403 pages. If unauthorized then redirect to our login page. Still need to experiment with this, but I though I seen something like that somewhere.

One note for reference:Using /etc/designs/<project name>/favicon.ico is 'old school'. We did update our code to '/etc.clientlibs/<projectname>/clientlibs/site/resources/favicon.ico' to be in line with the latest design recommendations(ps. do not forget allowProxy = true)

Thanks you. This is working, but how to you redirect to a login page. Did you customize the default 401-403 error pages to redirect to your login page?

@GirishBedekar Thank you for the reply. Not sure if this is still valid in AEM 6.5 as we do not have  AEM JEE running and the servlet is not working without this. In the end we did found that we could manual configure the "submitServiceProxy" value for the xfaforms\profiles. This will will then over...

So Coming back to my original question. There is no out-of-the box solution for the default submit action of a HTML template without AEM JEE installed?

Adaptive template still require a XDP as a DOR. to give the form structure and context. So we still need to develop XDP's In this case the client already has interactive PDF documents that can be saved as XDP so we can deploy these quite quickly with only a submit button. Then we have time to conver...

The final outcome will be a publish deployment for the form, not on author. Let us play around with it for a while. I do see that we might be able to put the "site" page on publish while the adaptive from is still on Author. Not sure if this will work but we will have a look at such a scenario.