How to remove alerts messages ,while opening a page ocurs of it in dispatcher URL | Community
Skip to main content
Y
YuvaRani14
July 27, 2020
Solved

How to remove alerts messages ,while opening a page ocurs of it in dispatcher URL

  • July 27, 2020
  • 2 replies
  • 895 views

In author and publish instances,opening a page working good,

while opening a same page in dispatcher url, alert messages arise like this site says not found  but i clicked OK then a page opens normally.

so i want to remove that alerts how to do that? can u tell 

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 vanegi

The cause of this issue is one of the following:

  • A misconfiguration in the dispatcher/filter section of the .any file where the dispatcher farm is defined.
  • Web server has rewrite rules that are rewriting the request to an incorrect path.
 
I. CHECK THE DISPATCHER CONFIGURATIONS

The first step to debug and solve this issue is to enable debug level logging in the web server configurations. For information on how to enable debug logging refer Configuring Dispatcher. 

Once debug logging is enabled, search for a line with "Filter rejects {request-line}". Here {request-line} is the request method and the url that is incorrectly returning 404. See the log messages below for an example of the request GET /libs/wcm/core/content/siteadmin.infinity.json HTTP/1.1:

 
 
cache-action for [/libs/wcm/core/content/siteadmin.infinity.json]: NONE [Tue Oct 16 13:47:18 2012] [D] [2880(1532)] connected to render publishl (127.0.0.1:4502) [Tue Oct 16 13:47:18 2012] [D] [2880(1332)] Filter rejects GET /libs/wcm/core/content/siteadmin.infinity.json HTl

 

If there is such a line, but the URL path has been modified ("rewritten") by the web server then see section II below. However, if the URL path matches what you expected to be sent to the publish instance then the /filter configuration of dispatcher farm is incorrect. For information on how to fix it, refer the article Troubleshoot Dispatcher flushing issues.

 

 

II. CHECK THE WEB SERVER REWRITE RULES

 

If the URL path being used by dispatcher is modified to a non-existent path, then it is likely caused by a bad rewrite rule configured in the web server. Review your web server rewrite rules, and find the respective documentation. Then, to find the rule that is unexpectedly changing the URL path review the rewrite rules.

2 replies

vanegi
Adobe Employee
vanegiAdobe EmployeeAccepted solution
Adobe Employee
July 27, 2020

The cause of this issue is one of the following:

  • A misconfiguration in the dispatcher/filter section of the .any file where the dispatcher farm is defined.
  • Web server has rewrite rules that are rewriting the request to an incorrect path.
 
I. CHECK THE DISPATCHER CONFIGURATIONS

The first step to debug and solve this issue is to enable debug level logging in the web server configurations. For information on how to enable debug logging refer Configuring Dispatcher. 

Once debug logging is enabled, search for a line with "Filter rejects {request-line}". Here {request-line} is the request method and the url that is incorrectly returning 404. See the log messages below for an example of the request GET /libs/wcm/core/content/siteadmin.infinity.json HTTP/1.1:

 
 
cache-action for [/libs/wcm/core/content/siteadmin.infinity.json]: NONE [Tue Oct 16 13:47:18 2012] [D] [2880(1532)] connected to render publishl (127.0.0.1:4502) [Tue Oct 16 13:47:18 2012] [D] [2880(1332)] Filter rejects GET /libs/wcm/core/content/siteadmin.infinity.json HTl

 

If there is such a line, but the URL path has been modified ("rewritten") by the web server then see section II below. However, if the URL path matches what you expected to be sent to the publish instance then the /filter configuration of dispatcher farm is incorrect. For information on how to fix it, refer the article Troubleshoot Dispatcher flushing issues.

 

 

II. CHECK THE WEB SERVER REWRITE RULES

 

If the URL path being used by dispatcher is modified to a non-existent path, then it is likely caused by a bad rewrite rule configured in the web server. Review your web server rewrite rules, and find the respective documentation. Then, to find the rule that is unexpectedly changing the URL path review the rewrite rules.

    sunjot16
    Adobe Employee
    sunjot16Adobe Employee
    Adobe Employee
    July 28, 2020

    It seems as if the dispatcher has some of your cached clientlibs. Try to reproduce the issue my removing the entire dispatcher cache.

     

      Terms & ConditionsAccessibility statement

      Loading footer...