http 302 redirect

Hi

What is your IIS default page name on you IIS server ? Is it 'index.html' ?

Cant you just tell your IIS server that if someone asks for "/", then serve up "default.aspx"

If that does not work/help and you want to use iRules, then you could certainly have a rule that says "if client asks for / , then serve /default.aspx"

Did you use HTTPWatch or HTTPFox to verify the client browser does not get the redirect to /default.aspx ?

I was wondering how you knew it was coming from the server, but not making it to the client ?

 when HTTP_REQUEST {
if { [HTTP::uri] equals "/" } {
HTTP::redirect "https://[HTTP::host]/default.aspx"
}

}

Ok .. APM changes things.

There are a lot or redirects that take place, and the standard HTTP_REQUEST events are not always going to fire as expected as there is some "hidden stuff" happening on the VIP that you don't get exposure to.

See HIDDEN EVENTS at

https://devcentral.f5.com/articles/http-event-order-access-policy-manager.UzNOCc_NvX4

For APM internal URIs, like /my.policy and /my.logout, the HTTP_REQUEST/HTTP_RESPONSE events don’t fire as you would expect beginning in v11.x. ..... However, with APM, if you require access in your iRules to these internal URIs, you can use the ACCESS::restrict_irule_events command in the CLIENT_ACCEPTED event to expose them. An example:

Hidden Events

when CLIENT_ACCEPTED {
     ACCESS::restrict_irule_events disable
 }

 when HTTP_REQUEST {
   if { [HTTP::uri] ends_with "/my.logout.php3?errorcode=19" }{ 
      HTTP::redirect "/"
    }
 }

You need a full HTTP Watch trace to see what is going on

No, Im saying if you do need an irule, then you may need to use the "ACCESS::restrict_irule_events disable" command.

You need a HTTPwatch (or HTTPFox in Firefox ... which is free) to see all the redirects, etc to fully understand where the "redirect gremlin" is.