APM + SharePoint 2013

Hi Michael, there is no RFE for this. You can open an SR with support and submit an RFE.

 

Other users have fixed it with STREAM::expression in an iRule. Or you might try to use only a stream profile.

 

-- gianrico

 

Did you deploy the APM using a deployment guide / iApp?

 

Microsoft SharePoint 2010 and 2013 (BIG-IP v11.4: LTM, APM, ASM, AFM, AAM)

 

Microsoft SharePoint 2010 and 2013 (BIG-IP v11-11.3.x: LTM, APM, ASM, WAM)

 

Also I would check out Appendix A: Configuring SharePoint Alternate Access Mappings to support SSL offload to see if that helps.

 

Hi, I was wondering if you've ever had any other findings on this. I too want to publish sharepoint 2013 as an APM portal application and I too am faced with these unicode URLs. Is there a chance you may have a follow up on this? thanks Bert

For this I wound up needing to write an irule to handle it manually. But since then we've changed a little bit on how we deploy SP so I haven't had to deal with this recently.

For this I wound up needing to write an irule to handle it manually. But since then we've changed a little bit on how we deploy SP so I haven't had to deal with this recently.

Well, I tried adding an intermediate virtual server which applies the stream adaptions before handing it over to APM for the rewrite in the portal application. Unfortunately I cannot get this to work properly. It made sense to try and fix the unicode first, before handing it off to APM. But I keep getting the wrong URLs in the response content on the client. I now tried to publish sharepoint in an APM+LTM combination, so the rewrite is handled exclusively by my stream profile. This works. But since sharepoint is no longer a webtop application, I need to configure SSO with my other access profiles. I believe this cannot work because the other access profiles use webtops and the sharepoint profile uses APM+LTM. The single domain cookie doesn't seem to work.. grrrr