While working on a support case recently, i came across this issue wherein we were trying to publish an application and there was a warning message generated in the web monitor logs about "POST without Content-Type not Allowed" while accessing it from a client machine.

The issue was that the request does not contain a Content-Type header, and the method used in the request was POST. According to the configuration of Forefront UAG, POST without a Content-Type header is not allowed by default.

To allow POST requests without a Content-Type header for this application, do the following;

We will discuss various scenarios related to accessing Citrix Presentation Server (Web Interface 3.0/4.0/4.5) and Citrix XenApp (Web Interface 5.0) from Mac OS 10 X machines which are published through UAG and IAG SP2 UP3(In general IAG SP2), but not configuration. For configuration, please follow the steps described at http://blogs.technet.com/b/edgeaccessblog/archive/2010/03/25/how-to-publish-citrix-xenapp-5-x-with-uag-2010.aspx

Details of components used in testing:

• UAG (without UP1) and IAG 2007 SP2 UP3
• Mac OS X 10.5.2 Leopard. Updated versions like 10.5.7 and 10.5.8 are also applicable.
• Safari 3.0.4 (5523.15) and Mozilla Firefox 3.6.3 but, all pictures shown here are of Safari 3.0.4((5523.15). It applies to all new versions of Safari 4.0 and Mozilla.

By default, UAG comes with only Citrix XenApp (Web Interface 5.0) template. We have created template for Citrix Presentation Server (Web Interface 3.0/4/0/4.5) in UAG copied from IAG SP2 UP3.

On few occassions you may encounter an issue wherein the nUAG appliance when started and joined to the domain for the first time will take long time to start and when it starts the MS Firewall service stays in "starting" state. This problem occurs mostly when user has not followed the quick start guide properly and continued with the steps one after the other. Two ways to resolve it;

#1 If you have already configured the nUAG appliance and now the MS Firewall service is not starting. 

It seems to be a bug in UAG when you try to publish File Access and Remote Desktop Services on the same server. When you add applications in UAG and you add RDS before File Access you will see the following warning in the Web Logs of UAG. Also, when you try to access the File Access in portal from a client machine then you will see an error " URL /Filesharing/ contains an illegal path ".