5

I noticed that in my logs there are a ton of entries like this:

5920 09:09:26 WARN Request is redirected to no layout page. Item: sitecore://web/{11111111-1111-1111-1111-111111111111}?lang=en&ver=1 Device: {FE5D7FDF-89C0-4D99-9AA3-B5FBD009C9F3} (/sitecore/layout/Devices/Default)

I am not seeing any odd visual behavior. Is there a way to further debug what issue is placing this into the logs.

I'm using Sitecore 8.1

  • Have you published the site, or are you running in Live Mode? – jammykam Sep 26 '16 at 21:59
  • @jammykam Published – eat-sleep-code Sep 27 '16 at 2:22
  • Are you seeing this on a CD or CMS instance? – Paul George Oct 31 '16 at 9:55
4

Try clearing this setting:

<setting name="RedirectURLPrefixes" value="/sitecore" />

If it makes a difference it's a reasonable assumption you got some less than ideal URLs going on in your solution. Like http://site.domain/sitecore/content/home/news - that type of thing.

  • After clearing the value, the errors still are recorded. – eat-sleep-code Sep 26 '16 at 21:24
4

This can happen in two cases -

  1. On CD server if there is no sitecore folder, and someone requested http://domain/sitecore (This will go to check /sitecore/ item, not folder)

  2. http://domain/?sc_itemid={11111111-1111-1111-1111-111111111111}

To know, from such URLs are requested, only easier option is track this is by checking IIS logs at the time of such errors

  • 1.) /sitecore folder definitely exists, if I unsecure the folder I can login to it, but the errors keeps going into the log. – eat-sleep-code Sep 26 '16 at 23:35
  • I don't follow how IIS logs help in this scenario, isn't the request being made domain/?sc_itemid={11111111-1111-1111-1111-111111111111} ? If so, won't the IIS logs just show the same thing ? – Paul George Oct 31 '16 at 10:01
  • In case of any custom development if "/sitecore" item is mapped as a context item by mistake or in case of selected as a content item in aliases, etc. it won't have domain/?sc_itemid={11111111-1111-1111-1111-111111111111} URL, but still referring that item. We can find such URLs from IIS Logs. – Yogesh Patel Oct 31 '16 at 19:49
1

Presumably one of your customizations is incorrectly generating urls to, or directly requesting the content node, which has no presentation.

One approach could be to add real-time logging to the solution and then try to find what generates the requests by accessing the site, backend and front, to visually see any correlation. You could then determine if the request is coming from the browser by checking the network panel, if it's not there, presume it's being requested by the server somehow. Scheduled tasks can do strange things out of normal context.

Perhaps there is a query or expression somewhere that is failing to find the expected node and ends up pointing to the top level item.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.