Content not able to access from dispatchers if we have "." in the folder name

could you share dispatcher log and dispatcher.any file?

Dispatcher filter is rejecting this request.

How can we allow this URL format in the dispatcher filters /content/dam/live/preview.1.14.1 ?

Thanks

You may to check dispatcher logs for more details. Also check if you have existing rewrite rule which may be affecting this request

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?

Any pointers for me on this how to decompose the URL with the "." in folder names?

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.

Thanks

Uma

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.

Jörg

@Jörg Hoh Still, AEM does not even allow to create a name with a dot. The title can anything, the name should not have a dot in it.

berliant​

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.)

Jörg