"No resource found" when accessed pages with dispatcher

[kishore_polsani]

Hi All,

We have recently performed in-place upgrade from AEM 6.1 to AEM 6.2. We are able to access pages (/content/kishore/en/test.html) with publisher, when I try to access page (/kishore/en/test.html) with dispatcher shortened URL, we are getting 404 errror. This shortened URL was working in AEM 6.1 version.

Error Message:

25.10.2017 06:56:28.392 *INFO* [10.204.139.61 [1508914588391] GET /kishore/en/test.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /kishore/en/test.html not found

25.10.2017 06:56:28.392 *INFO* [10.204.139.61 [1508914588391] GET /kishore/en/test.html HTTP/1.1] apps.sling.servlet.errorhandler.404$jsp 404:: Starting to work with: /kishore/en/test.html

25.10.2017 06:56:28.392 *INFO* [10.204.139.61 [1508914588391] GET /kishore/en/test.html HTTP/1.1] apps.sling.servlet.errorhandler.404$jsp 404:: Resource returned for current URL. Finding a 404 page in following content structure: /kishore/en/test.html

I have checked below options

• anonymous user has access read access.
• Default paths (resource.resolver.searchpath) are available in "Apache Sling Resource Resolver Factory" OSGI config. Is anything changed in AEM 6.2.
• No dispatcher rules have been updated.

Any idea what am I missing here?

Thanks,

Kishore

[VeenaVikraman]

so how are you setting up those shortened urls ? is it mapping or rewrite rules ?

[smacdonald2008]

This could be some sort of upgrade bug - do you have a fresh AEM instance to test with?

[kishore_polsani · Accepted solution]

This would help Https URL' resulting with 404 after in place upgrade of 6.2(6.1 to 6.2)