Highlighted

Vanity URL for Forms

sidharthc212039

19-06-2020

I would like to understand what is the best way to create Vanity URL for public facing forms.

For eg. consider a form which is rendered using a custom profile like this :

http://hostname:4502/content/profile/customProfile?contextRoot=crx:///content/dam/formsanddocuments/...

 

how can i mask the URL so that public facing link appears to be like:

http://hostname:4502/form1.xdp

or

http://hostname:4502/formStore/form1.xdp

I want to generalize the approach, so that a single config /mapping can be used for all the form templates which are located in the same folder.

Replies

Highlighted

sidharthc212039

22-06-2020

Hi Girish,

 

We have quite simple XDPs being simply rendered as HTML / Mobile form - for now. There's no pre populated data, and these forms do not trigger any workflow.

The user can fill the form online, and then click a button to generate a flattened PDF of their form, which can be later posted via email or conventional postage.

 

There's a custom render profile which introduces some minor cosmetic changes to toolbar.

All our forms are in a single folder under /content/dam/formsanddocuments/<folder>

 

There's a public portal which currently has links to PDF forms, and those will be replaced by these new links for rendering HTML forms.

While there will be a load balancer / webserver / dispatcher layer which will conceal the actual host where AEM is running, but we also want to conceal the structure of our rendering profile, or the folder where our forms are located, which gets exposed in the URL.

 

Highlighted

sidharthc212039

29-06-2020

thanks Mayank, however i dont see similar options for HTML forms. Secondly it appears that Vanity URL simply creates aesthetic URL, which eventually resolves to actual URL. I believe what i'm looking for is to mask the URL. I want to avoid showing the rendering profile and content repository path to my form, in my URL
Highlighted
Highlighted

sidharthc212039

30-06-2020

Hi Girish, our forms links are going to be put up on a website, which is not controlled by our department. therefore we wanted to have a layer of control, so that for minor changes we could use rewriting/masking layer to point to different URLs if needed. For eg. if render profile name changes, we wouldn't have to update all links on website, but simply update our rule for URL rewriting. I was finally able to do this by downloading the IIS rewrite module and creating a simple regex based rewrite rule. I'm going to keep an eye if anything behaves oddly and share with your guys. Thanks for your suggestions.