Restrict page.json to 404 page on aem 6.4 dispatcher | Community
Skip to main content
farahz913310
farahz913310
Level 2
February 25, 2019
Solved

Restrict page.json to 404 page on aem 6.4 dispatcher

  • February 25, 2019
  • 5 replies
  • 2519 views

Hi Team,

I am setting up the  dispatcher configuration for my site.

I need to restrict page.json to redirect to my site  404 page .

Can anyone help me on this .

Thanks.

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 joerghoh

If you want to disable the .json extension for all pages, I would recommend to reconfigure the Default Get Servlet and disable the JSON extension alltogether; that's the most reliable and easy to solve this problem. Do this only on publish, author instance requires that this is turned on.

Jörg

5 replies

Gaurav-Behl
Gaurav-Behl
Level 10
February 25, 2019

do you want to restrict "page.json" or  do you want to redirect it to 404 page?

is your 404 page served via apache or AEM?

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
February 25, 2019

/filter

  /0001 { glob "/home.json" /type "allow" }

/0002 { type "deny" /extension "json"}

farahz913310
farahz913310Author
Level 2
February 25, 2019

I am facing  a security issue if  user type .json at the end of url ,hence want it to go to my custom 404 page whenever user type .json at the end of any page url.

404 page is served by Apache currently

farahz913310
farahz913310Author
Level 2
February 25, 2019

Thanks @jorg. Just wanted to confirm ,adding these filters in my dispatcher ,will it cater for all urls if I insert .json at the end of  any url will it go to my custom  404 page.

Currently 404 is served from Apache

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
February 26, 2019

If you want to disable the .json extension for all pages, I would recommend to reconfigure the Default Get Servlet and disable the JSON extension alltogether; that's the most reliable and easy to solve this problem. Do this only on publish, author instance requires that this is turned on.

Jörg

    Terms & ConditionsAccessibility statement

    Loading footer...