Facing Issue In Touch UI Editor Mode On Passing URL Params Separated by '/'

[sureshl93367205]

Hi,

In our application there is an need to pass request prarams as '/'  separated instead of passing it in conventional way of  '?' followed by params seperated by '&' . Facing issue in Touch UI edit mode on passing URL params in mentioned way , the example URL is http://localhost:4502/editor.html/content/ccw/us/en/test.html/param1=val1/param2=val2

Page opens fine when navigated from other pages but it is throwing Page Not Found Error on refreshing it and when we directly navigate to specified page by providing the URL in the browser.

This issue is not coming up in classic UI edit mode and non-edit mode, page works fine on refresh, issue is only on touch-ui editor mode because of which page throwing an error on refreshing it after authoring the content.  AEM version used is 6.2 but observed this issue in other versions as well.

Any input on this would be helpful.

Thanks

[kautuk_sahni]

Hi

I am not sure, if this is right way to add params in the URL(Bad Practice). Can you please state the use-case of doing it by "/" insted of normal way?

To debug this, check the servlet resolution happening in classic UI and Touch Ui 

You can debug the Servlet resolution in 2 ways:-

Here’s one way:
1.    Head over to http://localhost:4502/system/console/servletresolver
2.    Enter the request URL and select the appropriate HTTP method (http://localhost:4502/editor.html/content/we-retail.html)
3.    The Opting servlets will be listed – I think the ‘chosen’ one is on the top

Please read my answer at :- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

This will help you deduce what is happening in both the cases.

I hope this would help you.

Thanks and Regards

Kautuk Sahni

[sureshl93367205]

Hi

Thanks for the response.  Request prarams are passed as '/'  separated instead of passing it in conventional way of  '?'  to enable caching of the URL in sling dispatcher.  Tried to figure out the reason for which it is failing in touch-ui based on your input but couldn't.

Thanks.

[kautuk_sahni]

Suresh L wrote...

Hi

Thanks for the response.  Request prarams are passed as '/'  separated instead of passing it in conventional way of  '?'  to enable caching of the URL in sling dispatcher.  Tried to figure out the reason for which it is failing in touch-ui based on your input but couldn't.

Thanks.

For that:

I think the config /ignoreUrlParams is what you can use. It can be used the white list query parameters which are used to determine whether a page is cached / delivered from cache or not.

Check http://docs.adobe.com/docs/en/dispatcher/disp-config.html#Ignoring%20URL%20Parametersfor details.

~kautuk

[kautuk_sahni]

kautuksahni wrote...

Suresh L wrote...

Hi

Thanks for the response.  Request prarams are passed as '/'  separated instead of passing it in conventional way of  '?'  to enable caching of the URL in sling dispatcher.  Tried to figure out the reason for which it is failing in touch-ui based on your input but couldn't.

Thanks.

For that:

I think the config /ignoreUrlParams is what you can use. It can be used the white list query parameters which are used to determine whether a page is cached / delivered from cache or not.

Check http://docs.adobe.com/docs/en/dispatcher/disp-config.html#Ignoring%20URL%20Parametersfor details.

~kautuk

Did my lst comment helped you ?

~kautuk