Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just enabled Failed Request Tracing for a site and I get a URL_CHANGED event as the third item on the log.

1. GENERAL_REQUEST_START SiteId="1", AppPoolId="DefaultAppPool", ConnId="1610613013", RawConnId="0", RequestURL="", RequestVerb="GET" 15:35:54.176 
2. GENERAL_SET_REQUEST_HEADER HeaderName="AspFilterSessionId", HeaderValue="", Replace="true" 15:35:54.192 
3. URL_CHANGED OldUrl="/test/wp-admin/", NewUrl="/index.php/test/wp-admin/" 15:35:54.192

Can someone tell me where the URL_CHANGED event comes from and how I can prevent it?

Update: The "default document" is set to "index.php" on our server. Could it be that the server automatically appends index.php to a path if the path does not specify a proper file or folder? I tried removing all "default document" entries but this didn't change the behavior...

Update2: I am still looking for an answer to this question... ;-)

share|improve this question

The URL_CHANGED message is usually an indicator that a URL re-write rule is being applied. You need to look at how you URL re-writing is configured in IIS to see why that is happening.

share|improve this answer
That's what I thought at first but the url rewrite rules don't kick in till event #6... – Ben May 12 '09 at 10:05

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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