Forum Discussion

Michael_Jenkins's avatar
Michael_Jenkins
Icon for Cirrostratus rankCirrostratus
Mar 17, 2015

APM + SharePoint 2013

We're trying to deploy SP2013 externally through an APM portal (with rewriting), which so far has been pretty decent. However, I've noticed that one thing SharePoint does is return content with URLs that are have some Unicode encoding (e.g.

http:\u002f\u002fwww.example.com\u002fsomepath
), so the rewrite profile does not catch those and rewrite them appropriately.

I'm sure I can "fix" this with a stream profile, but wanted to see if anyone else had dealt with this and whether there's ever been a RFE or something submitted regarding this issue.

Thanks, Michael

6 Replies

  • 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

     

  • 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