AEM 6.5 - Need clarification on externalizer/link checker/rewriter functionality working in OOTB we-retail pages.

cquser1

08-07-2019

Hi All,

We have set up 6.5 author and publish local machine.

On activation of page, for ex: http://localhost:4502/editor.html/content/we-retail/us/en/men.html and checking on publish

http://localhost:4503/content/we-retail/us/en/men.html for "Experience" section in footer, we see that "/content" is stripped off from

http://localhost:4503/we-retail/us/en/experience.html in publish.

Tried debugging multiple things to see how its working, but no luck.

Any thoughts/pointers on this will be helpful.

we-retail-publish.png

Accepted Solutions (1)

Accepted Solutions (1)

anujg3325839

08-07-2019

You can check few links -

1-  http://blogs.adobe.com/contentmanagement/2013/08/20/how-to-change-aems-redirection-http-st atus-code/

//

Redirection of request URLs in AEM can be configured at the Sling level, typically in the mapping configuration under /etc/map node. Depending on the requirements, there are times when customers would like to change the default HTTP status code for redirection. And here you will find two ways of changing the status code:

The sling:status way

Documented in http://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.ht ml already, you may use sling:status property to set a specific status code for a particular redirection. To extend the example given on the page linked above:

/etc/map
      +-- http
           +-- example.com.80
           |    +-- sling:redirect = "http://www.example.com/"
           |    +-- sling:status = "301"

Via OSGi configuration

Another way, which really sets the default for all redirection, is to configure the status code at the OSGi bundle level. In the OSGi console, browse the the Configuration page and locate:

“Apache Sling Resource Resolver Factory”

and change the redirect status field to whatever status code is appropriate (highlighted in diagram below).

[img]http://blogs.adobe.com/contentmanagement/files/2013/08/sling_redirection_status_code.png[/ img]

Another one can refer - http://aem-cq-tutorials.blogspot.in/2014/06/mapping-of-request-urls-in-cqaem.html

Hope it helps..

Thx, Anuj

Answers (2)

Answers (2)

vijkumar

10-07-2019

In addition to that check 'url mapping' field in  'Apache Sling Resource Resolver Factory' configuration, there could be a mapping there leading to the behavior. But it would impact all the urls, not just experience. /Content will be stripped from all urls having /content. If it is happening just for specific url check /etc/map

Nisha_Nivedita

Employee

09-07-2019

cquser1​ For your query "

"/content" is stripped off from

http://localhost:4503/we-retail/us/en/experience.html in publish."

>> Did you check in etc/map or sling:internal redirect rules? it should be stripping off from there. Rewriter is responsible for such behavior , so check rewrite config.