Developer forum

Forum » CMS - Standard features » Monitoring 404 URL resolve redundant?

Monitoring 404 URL resolve redundant?

Nuno Aguiar
Nuno Aguiar
Reply

Hi,

 

I am trying to get more familiar with the Monitoring log and found something odd here https://www.screencast.com/t/hfGv1fEYHIvv

 

I already understood that:

  • fullQueryString = the query string that was requested
  • pageid = the page id the user was redirected to (not the referrer - which would be helpfull by the way! can we add that?)
  • urlIndexName = I don't know yet

 

What's puzzling to me on this one in particular is that pageid 11875 is the 404 page for this website, so it seems like we're generating duplicate logs for every 404 (the real one + this one).

 

Am I reading this correctly?

 

Best Regards,

Nuno Aguiar


Replies

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

The record you show in your screendump is a "ghost chasing" log entry. We have seen some exceptions related to looking up URLs to show on pages - and from this record it seems to be related to pages with internal links being used as 404 pages.

So once we have figured out why this URLResolve issues is there, these events will go away.

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Nicolai,

 

When you say "internal links being used as 404 pages" do you mean:

  • Internally we're pointing to the 404 page
    OR
  • Internally we're pointing to a page/id that does not resolve, hence returning the 404

 

Best Regards,

Nuno Aguiar

 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

On the 404 page you have a link to another page that does not resolve to a friendly url. Either because the link [something is wrong] or because the link resolver cannot figure out something because it is on the 404 page... Maybe.

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Nicolai,

 

Thank you for the explanation. That makes more sense to me then.

 

BR Nuno

 

You must be logged in to post in the forum