Hi there,
I am working in ODC and I currently have 2 completely separate apps live. For both apps we have specific domains, "www.domain1.nl" and "www.domain2.nl".
However, for a user to reach this specific application, just filling out "www.domain1.nl" it not enough. Once a user does this, they will see "This "www.domain1.nl" page can’t be found". The user HAS to write "www.domain1.nl/appname/". Our competitors are far more easy to find this way, since they do not have this problem.
As you can imagine, my customer is not happy with this. I have contacted OS support and they say there is nothing they can do. It is "in the backlog" and "on the roadmap", without a specific release date. Could be years as far as I know.
We have looked into the DNS records, but there is nothing we can do. Only thing we did is make a .com version and redirect that one to our original. However, that is not a solution, since the customer wants the .nl working.
Are we the only one with this problem? Is there anything we can do?
I hope I have been clear enough in my explanation.
Kind regards
You can solve this by using a reverse proxy with NGINX. Configure the DNS to point to NGINX for www.domain1.nl. NGINX will then proxy pass the request to the ODC application.
Hi Alex. Did you solve your issue?
We have a very similar problem. We have three environments in OutSystems (Dev/Test/Prod), and an Azure Application Gateway in front of OutSystems. In Dev&Test everything works perfect, but in Prod, when we access the webApps without the context (/appname/) what we get is only a blank page. Adding the context (www.domain.com/appname/), they work perfect.
We already asked to OS support and their answer is that Reverse Proxy (Azure AppGateway) is not supported. Their only solution is to access the webApps directly to OS, using a custom certificate.
I have seen other guys saying that OS+ReverseProxy is a very bad idea, so we are exploring the option that OS support gave us.
Hi Elfego,
Our current workaround is to work with a iFrame. So we host a web page, where we have put a simple index.html file that refers to our application. That way, the application works without adding the context. However, it comes with the drawback that refreshing the page, will send you back to the homepage.
I hope this proves sufficient for your cause.
Kind regards,
Alex
Thanks, Alex, for your answer but I am a little lost.
About the iframe, are you mean something like <iframe src="https://web.app.com/context" ></iframe> ??
Do you have only one index.html? Where is it, in the "/" of backend? Or do you have one index.html on each webApp ?
Again, thanks so much for your answer.
We have a webhosting for our application. That webhosting already had a index.html file in place. We replaced that file with the file you can find in the attachment. Of course you have to add your own title and URL.
We only have one file in place. I hope this answers your question, otherwise I'd like to hear it.