Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

domain issue in publish env

Avatar

Level 1

Hi All,

We are facing an issue with domain.

Explanation:

we have one.html page under "/etc/designs/myproject/publicClientlibs/folder1/html/one.html"

we have a server having system name (system123) and domain is (application-myserver.one.com)

we are getting the page with these URLs :

Using System Name for  Author : http://system123:4502/etc/designs/myproject/publicClientlibs/folder1/html/one.html

Using System Name for publish : http://system123:4503/etc/designs/myproject/publicClientlibs/folder1/html/one.html

Using Domain Name for Author : http://application-myserver.one.com:4502/etc/designs/myproject/publicClientlibs/folder1/html/one.html

But we are getting 404 Page Not found for using domain name with publish

http://application-myserver.one.com:4503/etc/designs/myproject/publicClientlibs/folder1/html/one.html

Could any one please suggest what should be the reason for this behaviour?

Thanks in Advance

Radhika

1 Accepted Solution

Avatar

Correct answer by
Level 8

I can think of a number possible causes for the problem:

  1. What is the source of the 404 - is AEM's 404 or another system. If it's not and AEM 404 then perhaps you domain name mapping is incorrect. 
  2. Do you have any Sling mappings that are domain specific - if you sling mappings specific to the domain name then that might explain it. 
  3. If neither of those two situations are true then I'd suggest taking the following steps:
    1. Tail you request.log and error.log when you hit the URL you are interested in using the domain name and see if you get any clue as to what possible cause is - sometimes you'll see interesting messages with a 404.
    2. Go to recent requests page in the Felix admin console immediately after trying to access the page with the domain name and look at the request stack. This will very often tell you why Sling thinks that request is a 404 (mappings, JCR Resource Resolve configs, etc,). 

View solution in original post

5 Replies

Avatar

Level 8

Have you moved code to publish env and activated content?

Avatar

Level 3

Hi Everyone,

Thanks for your help 🙂

 

The issue is resolved now. The problem is due to one of the rule we set under \etc\design\map.publish is rewriting the url of html file. 

the original url published : http://application-myserver.one.com:4503/etc/designs/myproject/publicClientlibs/folder1/html/one.html

/content/myProject/en/ is appended as a prefix in the asset url which is causing the issue and redirected to page not found

http://application-myserver.one.com:4503/content/myProject/en/etc/designs/myproject/publicClientlibs....html 

 

We modify the rule and it started working.

Thanks,

RK

Avatar

Correct answer by
Level 8

I can think of a number possible causes for the problem:

  1. What is the source of the 404 - is AEM's 404 or another system. If it's not and AEM 404 then perhaps you domain name mapping is incorrect. 
  2. Do you have any Sling mappings that are domain specific - if you sling mappings specific to the domain name then that might explain it. 
  3. If neither of those two situations are true then I'd suggest taking the following steps:
    1. Tail you request.log and error.log when you hit the URL you are interested in using the domain name and see if you get any clue as to what possible cause is - sometimes you'll see interesting messages with a 404.
    2. Go to recent requests page in the Felix admin console immediately after trying to access the page with the domain name and look at the request stack. This will very often tell you why Sling thinks that request is a 404 (mappings, JCR Resource Resolve configs, etc,). 

Avatar

Level 1

Hi, 

Yes we activated the /etc/designs/myproject/publicClientlibs folders from Activate tree.

//RK

Avatar

Level 10

Hi RK,

Also make use of configuration  test at http://localhost:4503/system/console/jcrresolver

Thanks,
Sham
Twitter: @adobe_sham