We have migrated content from legacy to AEM DAM which is having the ".'" format in the folder names like "preview.1.41.1".
what are the options to access the content? Please advice.
Note: It's not possible to update the names, those are linked with different applications.
Solved! Go to Solution.
Can you give an example how this does not work? Can you share the requests you make to AEM (which are working well) and through the dispatcher (which seem to be problematic)? What are the relevant log entries for them? What plattform are you running the dispatcher on? Windows/Unix? IIS / Apache httpd? What version of the dispatcher are you using? How does your dispatcher.any look like?
If you can provide us information regarding this, we might be able to help you. I am not aware of any limitation in the dispatcher which prevents you from accessing folders with a "." in its name.
How did you manage to create a folder name with a dot? If you use TouchUI and create a folder with a title "preview.1.14.1" then the fodler name can be either "preview-1-14-1" or "preview1141". The UI would not even allow you to create a folder with a dot in the name.
The reason for that is that a dot suggests that there is a selector and it will try to find a script to render a resource:
The sling URL decomposition does not break if your resource contains a "." in it. Just tested it locally. And that's because the decomposition does not use a string to work on, and split on every "." character, but first identifies the resource. And then it doesn't matter how much "." characters the resource name contains.
(Just tested it locally.)
Just for the sake of demonstration:
* In CRXDE Lite I renamed /content/we-retail/us/en/experience/skitouring to /content/we-retail/us/en/experience/skitouring.joerghoh
* then I requested localhost:4502/content/we-retail/us/en/experience/skitouring.joerghoh.html and it worked.
The fact, that within AEM you cannot use the "." character does not necessarily mean, that it does not work in underlying layers. There might be limitations where a "." is not working well, but for Sling resource resolution a "." in the resource name is not a problem.
I am able to access the files by using directly Author and in Publishers but from dispatcher, it's returning 404.
Yes, you are right AEM won't allow us to create a folder with "." but this is migrated content we copied by using the WebDAV and packaged from one instance to another instance.
We don't have the option to rename the folder since the same name used by the vendor and legacy application.
What options do we have to access these files from dispatchers? Please advice.
I'm able to access '/content/dam/live/preview.1.14.1/image.jpg' via apache 2.2/dispatcher/WIN and its getting cached without any errors.
Can you share relevant log files and screenshots and other info?