Forum Discussion
OWA 2007 and ASM OWA Template
Hello All,
I am currently working on testing 9.4.3 on our test box in preperation for ugrading our production ASM boxes. I wanted to setup these VIPs using the OWA Template, but I noticed the documentation specifies OWA 2003. So I have 2 questions about that one is there anything in this template that would not work with OWA 2007? Fairly broad, but just thought I should ask. The second question has more to do with the exert from the documentatio below.
"... 4. For the Dynamic Sessions in URL setting, select Custom pattern,
and then in the Value box, type the following regular expression:
(?<=\/exchange\/)([^\/"]+)
My question about this is that it appears that this regex is to allow dynamic session in /exchange uri but OWA 2007 uses /OWA not /exchange. So I am wondering if replacing exchange with OWA in this regex would work? Or maybe I am missing the point of this regex???
4 Replies
- Am I the only one running Exchange 2007 / OWA / CAS through ASM?
hoolioCirrostratus
I haven't implemented ASM for Exchange 2007 OWA, but I can see in 2003, that dynamic session in URI regex is logically removing the user's name from the URIs which ASM parses.
Using the regex you first noted:
(?<=\/exchange\/)([^\/"]+)
the user name will be logically removed from these example URI's:
/exchange/my.user/Inbox/my_subject.EML?Cmd=open
/exchange/my.user/Tasks/?Cmd=contents
/exchange/my.user/Inbox/?Cmd=contents&Page=1&View=Messages
So if the only difference in OWA 2007 is that the prefix is OWA instead of exchange, you could change the regex to (?<=\/OWA\/)(?:[^\/"]+). Note that the supplied regex should include a ?: to prevent an unnecessary capture of the match into a back reference.
With the regex configured correctly, you shouldn't see the username in the URIs logged in ASM. So if you try the modified regex and do see the username in the URIs, reply with some examples and we can take another look.
Hope this helps,
Aaron- hoolioActually, this regex is a bit more concise and logically removes the slash after the username:
(?<=/OWA/)(?:[^/"]+/)
So this:
/OWA/user.name/Tasks/?Cmd=contents
is logically parsed as this:
/OWA/Tasks/?Cmd=contents
Aaron - I am working on building a policy for Exchange 2007 as well, but our CAS servers service both Exchange 2003 and Exchange 2007 backend servers so I need to support /exchange and /OWA. Does anyone have any thoughts on how to handle this?
