Dispatcher rules to block secured paths | Community
Skip to main content
S
srinivasanp3053
New Participant
June 19, 2023
Solved

Dispatcher rules to block secured paths

  • June 19, 2023
  • 3 replies
  • 1652 views

Hi,

 

We are using AMS 6.5 SP15. The following paths are being exposed and json responses are rendered from the dispatcher. 

 

content paths:

===========

/content/.2.json;%0Aa.png/.json

/content/projectfolder/.5.json;%0Aa.png/.json

/content/.2.json;%0Aa.png/.json

/content/proj/us/en/b-content/page-billing/jcr:content/root/container/container/authcontainer/testcomponent-copy-par-c/par_1.100.json;%0AXLA.ico/a.html

 

dam paths:

========

/content/dam/proj-assets/en-us/brandname/images.1.json;%0Aa.png/.png

/content/dam/test-library/en-us/fol1/folder2/.children.json;%0AXLA.ico/a.html

/content/dam/test-library/en-us/fol1/folder2/pdf/test1.pdf/.children.json

 

Can you suggest some generic filter rules to block these paths in the dispatcher filter rules?

 

Thanks in Advance.

 

Regards,

S

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by MayurSatav

Hi @srinivasanp3053 ,

you can use the following rules :

 

For blocking content paths:

/0001 { /type "deny" /glob "/content/*.json" } /0002 { /type "deny" /glob "/content/**/*.json" }

 

For blocking DAM paths:

 

/0003 { /type "deny" /glob "/content/dam/*.json" } /0004 { /type "deny" /glob "/content/dam/**/*.json" }

 

 

3 replies

Nishant-Singh
Nishant-Singh
Employee
June 19, 2023

You can use advanced Dispatcher filter rules to block paths with the help of path, selectors, extensions etc.

Example 

/006 { /type "deny" /path "/content/*" /extension '(json|xml|feed))' }

 

    aanchal-sikka
    aanchal-sikka
    New Participant
    June 19, 2023

    @srinivasanp3053 

     

    You might want to revisit the existing rules as well

    Ideally, on publish instances you should start with Deny access to all content

    /0001 { /type "deny"  /url "*" }

    Next,  we should not enable the json paths that are required. Example

    /0251 { /type "allow" /selectors "model" /extension "json" /path "/content/abc/*" }

     

    It would help, if you could provide more details:

    1. Are these json available across all content, and you want to avoid for all. If yes, please have a look at the configs shared above.

     

    2. Is it only the secured content, where you want to avoid json. How are these restricted?

    Aanchal Sikka
      MayurSatav
      MayurSatavAccepted solution
      New Participant
      June 19, 2023

      Hi @srinivasanp3053 ,

      you can use the following rules :

       

      For blocking content paths:

      /0001 { /type "deny" /glob "/content/*.json" } /0002 { /type "deny" /glob "/content/**/*.json" }

       

      For blocking DAM paths:

       

      /0003 { /type "deny" /glob "/content/dam/*.json" } /0004 { /type "deny" /glob "/content/dam/**/*.json" }

       

       

        Terms & ConditionsAccessibility statement

        Loading footer...