Hi DariaSuleimanova,Filter will work without this property. For my situation, I want to restrict my custom filter to certain servlet, so I use the sling.filter.pattern property. @Component(service = Filter.class, property = {                    Constants.SERVICE_DESCRIPTION + "=My Filter",          ...

Hi DariaSuleimanova,In my custom filter, there is a sling.filter.pattern property, but what I use is "pattern", so this filter cause the problem. After I changed it to "sling.filter.pattern", the 404 page shows correctly.

I figure out the problem of the custom filter, the pattern that restricts the filter to the target servlet has a wrong setting. Now I change it to the correct setting, the 404 Page works correctly now. Thank you for all your help!

Hi antoniom54959291I tried changing the setStatus code in the errorhandler, the response still gets 200 for invalid url. I then stop the bundle that includes a custom filter (as suggested by @berliant​berliantTherefore, it is the custom filter that causes the issue. I am still struggling on fixing t...

Hi, antoniom54959291Thank you for your response. Do you mean that use this method in the Filter.java?

Hi berliant,In the custom filter, I actually add the logic to check the request URI, if it is not the path of the target servlet, the filter won't do anything (I use filterChain.doFilter(request, response) for this situation). Somehow I don't know why the response status code is always 200. If I put...

Hi berliant,Thank you for your reply. I have one custom filter that sets status code to 400 if the slinghttprequest does not satisfy certain condition. After I stopped the custom bundle, the 404 not found status code shows up correctly. However, this custom bundle is also needed in the project, is t...

Hi himanshusinghal,I just tried to increase the size to different sizes. No matter how many size I increased, I still got the 200 status code and the blank page.

Hi himanshusinghal,Yes, I still got the 200 status code even after I doubled the response buffer size.

Hello cal-netsolutions,Thank you for your suggestion. However, we have implemented a custom error handler. It works fine in Publish instance in another computer. It does not work in some computers and the stage. They have the same problem: invalid url always got 200 status code with blank page.