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
BedrockMission!

Learn More

View all

Sign in to view all badges

trying to add a simple rule to default_filters.any, but failing with enforce-checksum-of-immutable-files error.

Avatar

Avatar
Ignite 10
Level 4
TB3dock
Level 4

Likes

34 likes

Total Posts

203 posts

Correct Reply

4 solutions
Top badges earned
Ignite 10
Boost 25
Give Back 25
Validate 10
Validate 1
View profile

Avatar
Ignite 10
Level 4
TB3dock
Level 4

Likes

34 likes

Total Posts

203 posts

Correct Reply

4 solutions
Top badges earned
Ignite 10
Boost 25
Give Back 25
Validate 10
Validate 1
View profile
TB3dock
Level 4

11-05-2021

We are trying to get a servlet visible in the publisher, and understand we have to add a rule to the dispatcher.

Build works fine against the local cloud SDK, but when the source is pushed to cloud, build fails with:

 

There have been changes detected in a file which is supposed to be immutable according to https://docs.adobe.com/content/help/en/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#file-structure: src/conf.dispatcher.d/filters/default_filters.any

 

We are trying to make our servlets on /bin/xxx visible, and this is the way to do it:

/005 { /type "allow" /url "/bin/*"    }  # allow bin path access

We tried adding this line to myapp.dispatcher.cloud/src/conf.dispatcher.d/filters/filters.any, but this had no effect.

Next we tried commenting out the line which already existed in default_filters.any, but this results in the above build error.

 

Any ideas how to make a servlet path visible on publish instance?

 

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,345 likes

Total Posts

3,220 posts

Correct Reply

914 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,345 likes

Total Posts

3,220 posts

Correct Reply

914 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

12-05-2021

Hi,

Please update filters.any file.

defualt_filter changes will not be reflected if you directly made changes there.

e.g. of filters.any

 

$include "./default_filters.any"

#### Custom rules
/0100 { /type "allow" /path "/content/myproj/*"  /extension '(html|jsp|json|pdf)' }

 

 

Answers (2)

Answers (2)

Avatar

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

224 likes

Total Posts

283 posts

Correct Reply

65 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile

Avatar
Springboard
MVP
Shashi_Mulugu
MVP

Likes

224 likes

Total Posts

283 posts

Correct Reply

65 solutions
Top badges earned
Springboard
Bedrock
Validate 1
Applaud 100
Establish
View profile
Shashi_Mulugu
MVP

12-05-2021

@TB3dock As per the documentation, you should not touch any OOTB files came by default from archetype or AMS.

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/content-delive...

 

You should create your custom farm in available farms directory, and include custom filters file and then put your logic in that, make that custom farm in enabled farms as softlink.

Avatar

Avatar
Give Back 100
Level 10
asutosh_jena
Level 10

Likes

544 likes

Total Posts

663 posts

Correct Reply

190 solutions
Top badges earned
Give Back 100
Boost 500
Affirm 100
Ignite 1
Establish
View profile

Avatar
Give Back 100
Level 10
asutosh_jena
Level 10

Likes

544 likes

Total Posts

663 posts

Correct Reply

190 solutions
Top badges earned
Give Back 100
Boost 500
Affirm 100
Ignite 1
Establish
View profile
asutosh_jena
Level 10

11-05-2021

Hi @TB3dock 

 

Here is the sample path:

asutosh_jena_0-1620797577313.png

 

ams_publish_filter.any will be used for the publish instance.

 

You can identify which file is mapped for publish by going to 999_ams_publish_farm.any and check for the filter section which will show which file is loading for the filter rules.

 

/filter {
$include "../filters/ams_publish_filters.any"
}

 

 

# deny everything and allow specific entries
# Start with everything blocked as a safeguard and open things customers need and what's safe OOTB
/0001 { /type "deny" /url "*" }

# Open consoles if this isn't a production environment by uncommenting the next few lines
# /002 { /type "allow" /url "/crx/*" } # allow content repository
# /003 { /type "allow" /url "/system/*" } # allow OSGi console

# allow non-public content directories if this isn't a production environment by uncommenting the next few lines
# /004 { /type "allow" /url "/apps/*" } # allow apps access
/005 { /type "allow" /url "/bin/*" } # allow bin path access

 Also try changing the rule numbers such as if 005 is not taking put something like 007 or 111 and try it out.