Does AEM 6.1 support .com for the folder name?

Yes mate, you can't do this though UI but you can do this using CRXDe. On the other note you probably should not do this for many reasons. You need to do this level of abstraction at Dispatcher level with VirtualHosts and rewrite rules.

It should support .com in the node name. Did you try creating a new node with .com and checked if the same issue persists ?

When we create any site with dot in name from site admin. AEM is automatically changing the dot to - hyphen (Example when i created with "test.com" AEM replaced the . with - in name).

After creating if we are renaming the site to test.com and save (/test-com/ renamed )to test.com from crx/de). I am able to see the page rendered properly (http://localhost:4502/content/test.com/test123.html ). My AEM version is Version 6.1.0.SP2.

I think you have issue with not  .com name. There might be some thing else at the template level or the components that got dragged and dropped on to that page. Can you check the logs once.

Hi,

Can you please check the request, which returns with the 302, in the browser with the developer tools? I would like to know where the redirect is going to ("Location" header of the response).

What happens when you use this url: https://example.com/sites.html/content/identity.com/ca/testpage.html​ (note the .html at the end)?

kind regards,
Jörg

Hi Veena

Here are the screenshots...

Thanks Veena, really appreciate the details.

Agree, the naming conventions not correct; the folder was created by others

to support a business use case.

Interesting to know you were able to open & edit page in .com folder; I was

not able to open/edit in all our environments- local,dev,qa &production.

attached the screenshots.

something to do with AEM version? we use Adobe Experience Manager, Version

6.1.0.20150804

thanks

Guru

Hi Jorg

I get HTTP/1.1 302 Found;

not finding much info in server logs; in browser logs i see HTTP 302.

I'm able to reproduce the issue locally - created  2 folders with same content: identity.com & identity-com; i was able to open & edit content under identity-com.

-Guru

I would do folder-names like .com, perhaps it is supported. But I guess you run into issues later on.

Hi Guru,

What do you mean with "not able to edit"? Is there any exception in the log, and javascript error in the browser console? Can you reproduce the problem locally?

Jörg