File uploads do not occur to SharePoint Server 2013 or OneDrive for Business through Forefront Unified Access Gateway 2010

Applies to: Forefront Unified Access Gateway 2010Microsoft Forefront Unified Access Gateway 2010 Service Pack 1


When you try to upload a file to a Microsoft SharePoint Server 2013 document library or to OneDrive for Business through Microsoft Forefront Unified Access Gateway (UAG) 2010, nothing happens when you click OK.


This problem occurs because of an error in an application wrapper (AppWrap) in Forefront UAG. The AppWrap manipulates the HTML response body that is returned from SharePoint Server 2013.


To resolve this problem, install Service Pack 4 for Microsoft Forefront Unified Access Gateway 2010.


To work around this problem, create the following file and save it as WhlFiltAppWrap_HTTPS.xml in the following location:

%Program Files%\Microsoft Forefront Unified Access Gateway\von\Conf\WebSites\trunk_name\conf\CustomUpdate

Note If you use an HTTP trunk, save the file as WhlFiltAppWrap_HTTP.xml.

<APP_WRAP ver="1.0" id="RemoteAccess_HTTPS.xml">
<!-- Sharepoint 15 prevent upload from ribbon when policy is set to false-->
<URL case_sensitive="false">.*Upload.aspx.*</URL>
<SAR conditional_variable="Hybrid_WhlStatusFlagW" conditional_var_value="FALSE">
<SEARCH encoding="base64">b25jbGljaz0icHJvY2Vzc0lucHV0KCk7SEARCH>
<REPLACE encoding="base64">DQogICAgICAgICAgICAgICAgb25jbGljaz0iaWYgKCAodHlwZW9mKHdobF9jaGVja3VwbG9hZFBvbGljeSkgPT0gJ2Z1bmN0aW9uJykgJiYgKHdobF9jaGVja3VwbG9hZFBvbGljeSgpIT10cnVlKSkNCiAgICAgICAgew0KICAgICAgICB3aGxfYWxlcnRtZXNzYWdlKCk7DQogICAgICAgIHJldHVybiBmYWxzZTsNCiAgICAgICAgfQ0KICAgICAgICBlbHNlew0KICAgICAgICBwcm9jZXNzSW5wdXQoKTsgICAgICA=</REPLACE>
<SAR conditional_variable="Hybrid_WhlStatusFlagW" conditional_var_value="FALSE">
<SEARCH encoding="base64">IiBuYW1lPSJjdGwwMCRQbGFjZUhvbGRlck1haW4kY3RsMDAkUnB0Q29udHJvbHMkYnRuT0s=</SEARCH>
<REPLACE encoding="base64">ICAgICAgICB9IiBuYW1lPSJjdGwwMCRQbGFjZUhvbGRlck1haW4kY3RsMDAkUnB0Q29udHJvbHMkYnRuT0s=</REPLACE>


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


See the terminology Microsoft uses to describe software updates.