This content has been marked as final. Show 7 replies
Thanks for your question. At this time, you can use standard DNS interactions to redirect your URL to your Database Cloud Service, but that will just be the initial page. After that, the URLs will still be the longer form. We are planning to offer friendlier URLs in an upcoming release.
Hope this helps.
- Rick Greenwald
may be I don't understand you right...
I have trial instance and test application here at https://database-trialajnn.db.us1.oraclecloudapps.com/apex/f?p=1500304
database-trialajnn.db.us1.oraclecloudapps.com - it's 188.8.131.52 IP
I write to my domain this IP = login.ds24.ru
But when I test https://login.ds24.ru/apex/f?p=1500304
It is not work and write that url is wrong for this ssl sertificate
If I understand you correct now it's impossible use simple URL to login at application for example login.ds24.ru
Hi Rick, do you know approximately when "friendly URLs" (DNS CNAME records I presume) will be supported? This is a show-stopper for us running any production apps in db cloud. I'm not a fan of advertising the technology in the URL as it will only confuse the most important people (the users). Similarly, the /apex is fine when the user is a developer, but for regular App users it would be better if there could be an alias like /a
Hi Darrin -
We aren't really allowed to talk about future dates, because of revenue recognition guidelines, among other things, but I can tell you that this is extremely high on our priority list.
I will definitely post when we have a definite date. Other users have asked for the same thing, with the additional information that this is an absolute requirement for production, but not for the initial development stages. It sounds like your request is similar, yes?
And thanks for your interest.
- Rick Greenwald
Yes my request is similar. We will use db cloud for development for now with the plan to try production when custom domains / friendly URLs is supported. As I mentioned, I also like the idea of supporting /a context root in addition to (or instead of) /apex as we would prefer that our underlying technology be hidden from the users.