You'll need an HTTP profile on the port 80 virtual server in order to use that iRule to redirect all HTTP traffic to HTTPS. You wouldn't want to apply the same iRule to the 443 virtual server or you'd trigger infinite redirects to itself. If you want to have TMM parse the traffic as HTTP you could add an HTTP profile to the port 443 virtual server. Some specific examples of why you'd want to do this are:
compression
ram cache
layer 7 persistence like cookie persistence
layer 7 load balancing (using HTTP classes or iRules)
HTTP redirect if all the current pool member can't be reached (fall back host in the HTTP profile)
rewriting HTTP redirects that the application sends from http:// to https:// (option in the HTTP profile)
and many other options listed in the HTTP profile.
Aaron
Nimbostratus
