Forum Discussion
mikeshimkus_111
Dec 27, 2011Historic F5 Account
Here's a modified version of the iRule that will be included with the next version of the Exchange 2010 iApp. It includes log statements that you can remove if you like.
when HTTP_REQUEST {
switch -glob -- [string tolower [HTTP::path]] {
"/microsoft-server-activesync" {
log local0. "ActiveSync URI detected"
persist source_addr
pool Exchange_2010__single_as_pool
return
}
"/rpc/rpcproxy.dll" {
log local0. "OutlookAnywhere URI detected"
switch -glob [string tolower [HTTP::header "User-Agent"]] {
"msrpc" {
if { [HTTP::cookie exists "OutlookSession"] } {
persist uie [HTTP::cookie "OutlookSession"] 7200
} else {
persist uie [HTTP::header "Authorization"] 7200
}
}
"*microsoft office*" {
persist uie [HTTP::header "Authorization"] 7200
}
default {
persist source_addr
}
}
Finally, this assigns the Outlook Anywhere pool.
pool Exchange_2010__single_oa_pool
return
}
default {
log local0. "Fall through to default"
persist cookie
pool Exchange_2010__single_owa_pool
}
}
}
Also, here's the iRule we recommend for your OWA redirect:
when HTTP_REQUEST {
if { ([HTTP::uri] == "/") } {
HTTP::uri /owa/
}
}
- Hank_Moody_3649Apr 23, 2019Nimbostratus
Quote: Also, here's the iRule we recommend for your OWA redirect:
when HTTP_REQUEST { if { ([HTTP::uri] == "/") } { HTTP::uri /owa/ } }
Does this work also for the 2016er iApp? We have also problems with activesync.. My iRule does look like this:
priority 900 when HTTP_REQUEST { if { ([HTTP::uri] == "/") } { HTTP::redirect https://[HTTP::host]/owa/ } }
- boneyardApr 23, 2019MVP
i doubt your active sync issues are related to the OWA redirect.
if you used the 2016 iApp then that should take care of these things, there is no reason to fiddle with them unless you are doing some very different things.