After quite a long break, I've come back to do some work on our Sharepoint-based Portal. I went to our test server and found that, when I click on a link to a sub-page, the main page gets reloaded. This happens for all the sub-pages on the main page.
I checked the logs and see that the sub-page does get loaded. The last message in the log seems to suggest that the sub-page was found. There are no error messages.
Firebug shows that the sub-page is requested but a 302 return code is sent and the main page is reloaded.
I have looked in the ULS logs and I can se no indication of an error. Here is a part of the logs where the requested page (Support-Sitzung.aspx) is handled and then the home page (Portal.aspx) appears in the log.
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Usage Infrastructure d0i2 Verbose Successfully added requestUsageEntry to CollectUsageData with url http://portalt/company/intranet/en/Pages/Support-Sitzung.aspx 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring b4ly Verbose Leaving Monitored Scope (LogRequestUsage). Execution Time=0.0536381020492828 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____SQL Query Count=0 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Execution Time=0.0536381020492828 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nasq Verbose Entering monitored scope (ForceDehydrateHttpContextWorkflows) 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring b4ly Verbose Leaving Monitored Scope (ForceDehydrateHttpContextWorkflows). Execution Time=0.00446984183744023 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Execution Time=0.00446984183744023 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nasq Verbose Entering monitored scope (EndRequestHandler SPRequest Disposal) 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation General narq Verbose Releasing SPRequest with allocation Id {244607AB-30E6-40A5-8B74-56803403FD9D} 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring b4ly Verbose Leaving Monitored Scope (EndRequestHandler SPRequest Disposal). Execution Time=0.273498447428374 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____SQL Query Count=0 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Execution Time=0.273498447428374 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Usage Infrastructure d0hz Verbose Starting write trace for type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 0d4913d2-af73-4d2a-8540-7ee5f592ac95 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Usage Infrastructure d0i0 Verbose Successful wrote trace for type Microsoft.SharePoint.Administration.SPRequestUsageEntry with correlationID 0d4913d2-af73-4d2a-8540-7ee5f592ac95 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (GET:http://portalt:80/company/intranet/en/Pages/Support-Sitzung.aspx)). Execution Time=65.2677924149578 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____SPRequest Objects=3 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____SQL Query Count=6 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Execution Time=65.2677924149578 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Current User=XXX\myuser 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____WebPart Events Offsets=1 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Service Calls=0 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Page Checkout Level=Draft 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Current SharePoint Operations=0 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Critical Events=0 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Monitoring nass Verbose ____Log Correlation Id=0d4913d2-af73-4d2a-8540-7ee5f592ac95 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.33 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Logging Correlation Data 77a3 Verbose Ending correlation. 0d4913d2-af73-4d2a-8540-7ee5f592ac95
01.07.2013 10:02:43.34 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation Logging Correlation Data 9gc5 Verbose Thread change; resetting trace level override to 0; resetting correlation to empty list
01.07.2013 10:02:43.34 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation General 6t8b Verbose Looking up context site http://portalt:80/company/intranet/en/Pages/Portal.aspx in the farm SharePoint_Config
01.07.2013 10:02:43.34 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation General 6t8d Verbose Looking up the additional information about the typical site http://portalt:80/company/intranet/en/Pages/Portal.aspx.
01.07.2013 10:02:43.34 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation General 6t8f Verbose Site lookup is replacing http://portalt:80/company/intranet/en/Pages/Portal.aspx with the alternate access url http://portalt.
01.07.2013 10:02:43.34 w3wp.exe (0x1700) 0x0DEC SharePoint Foundation General 6t8g Verbose Looking up typical site http://portalt:80/company/intranet/en/Pages/Portal.aspx in web application SPWebApplication Name=SharePoint - 80.
I also notice that, if I open a browser on the server directly and go to one of these sub-pages, then there is no redirection - it works.
Has anyone else had this? Any suggestion where I might look for more information?
UPDATE
I just had a closer look at the Sharepoint logs and saw that the page request is recognised but then this message comes:
Site lookup is replacing http://servername:80/acme/intranet/de/Seiten/Favoriten.aspx with the alternate access url http://servername
It really is a long time since I set up this portal. What is meant by 'alternate access' and what might cause it to trigger at this point?
Seems this is normal behaviour so I'm still stuck with the original problem as to why the redirect occurs.
CLARIFICATION
-- I enter http://portalt
in the browser and land on http://portalt/company/intranet/en/Pages/Portal.aspx
(correct behaviour)
-- I click on a link 'Favourites' and land back on http://portalt/company/intranet/en/Pages/Portal.aspx
(http://portalt/company/intranet/en/Pages/Favourites.aspx
is expected)
The correct behaviour occurs in browser on the server.
In IIS, the host bindings contain just http, *:80
Alternate access mapping: (internal)http://portalt
; (Zone)Default; (public)http://portalt
FURTHER UPDATE
I was surprised to see that (so far) only my IE and Firefox that have the problem. Chrome works fine. In Firebug I see that the requested page returns 302 and then the main page gets reloaded. In Chrome the requested page returns 200 and continues to load. Strange!