none
Forefront Unified Access Gateway (UAG) - Problem with Parentheses in URL RRS feed

  • Question

  • I have noticed an issue with our UAG while accessing a document on our SharePoint server when passing an http link with a parentheses in it.  

    For example on our sharepoint server i have a doc located at http://spserver/docs/mydocument (1).pdf.   When accessing directly to the SharePoint farm the link works.  Also have success when going through the uag when accessing: https://spserver/docs/mydocument (1).pdf.   

    I do have a failure when i access the url  http://spserver/docs/mydocument (1).pdf.  When looking through the security event log I see error 

         The request from source ip address xx.xx.xx.xx, user to trunk xxxxxx, Secure=0 failed due to an error with a predefined global rule. The error code is Illegal character- (().

    I've tried to modify Global url character Rules, and add a URL set, but was unsuccessful.  

    I do have a few workarounds to the issue. 

    1. rename the document and have folks get an email with new link.   

    2. tell folks to use https externally vs the expected auto redirect from http to https.  

    3. url encode in the mailed out links %28 & %29 for the ( & ) parentheses.  

    Is there a way to allow UAG to accept the parenthesis on http connections?

    Thanks in advance.


    Joe--

    Wednesday, January 3, 2018 8:00 PM

All replies

  • While I don't have a direct answer to your question because I haven't tried this scenario before, it is interesting that it works properly on HTTPS. I do remember from UAG experience that there are numerous scenarios where when you make changes to your HTTPS trunks, you must delete and recreate the HTTP to HTTPS redirect trunk in order for those changes to be reflected inside the redirect trunk. Even though UAG never told you that you needed to do that, we were in the habit of pretty much any change you made to the primary portal/trunk, you just went ahead and deleted/recreated the redirect out of habit to make sure the settings were reflected there as well. Might be worth a shot.

    Friday, January 12, 2018 2:27 PM