Dispatcher log shows undefined in the requested url

[rishabhkrishan]

I am seeing a lot of 404 entry in the dispatcher error logs.

For example, 

"GET /page1/page2/undefined HTTP/1.1" 404 696 "https://www.brand.co.lang/page1/page2/page3.html"

Even though the page being accessed here i.e. page3 is available on Publisher instance. 

Also lets say if page3 has an alias set called 'page3-alias' logs shows below entry,

"GET /page1/page2/undefined HTTP/1.1" 404 696 "https://www.brand.co.lang/page1/page2/page3-alias.html"

There are warnings and error coming due to mod security that was installed on dispatchers. Not sure if they are blockers.

mod_include: Options +Includes (or IncludesNoExec) wasn't set, INCLUDES filter removed: /content/brand/worldwide/country/lang/index/page1/page2/undefined, referer: https://www.brand.co.lang/page1/page2/page3-alias.html

Is this a issue with code or dispatcher config or some already known issue with Mod Security module.

[Rite18]

@rishabhkrishan  could be due to the filter rule causing url to unidentified, refer dispatcher.any and validate the filter for allow path against the URL you are accessing 

[MukeshYadav_]

Hi @rishabhkrishan ,

Regarding INCLUDES filter removed check if the rules are placed correctly
https://stackoverflow.com/questions/19200522/apache-not-processing-basic-ssi

https://talk.plesk.com/threads/can-anyone-tell-me-what-this-warning-means.342337/

Is undefined getting appended in all the url accessed, if it is the case you may cross check rewrite rules if any extra param is expected like $1,$2 etc

Thanks

[rishabhkrishan · Accepted solution]

This issue was found to be a code issue. The thing is there are certain calls being made from FE code which has undefined in the URL in the first place. This was not after rewriting or anything to do with mod security. 

Dispatcher log entries were showing correct URLs. My take on this issue was in opposite direction.

Thanks folks for the help !