Request A Quote

Iron Networks Blog

why choose iron Software Define Data Center Hnv Hybrid Cloud Gateway MCE Cloud Edge Gateway Cloudboxx, branch-in-a-box Wss, windows storage systems

Archive - Jul 2010

Date
  • All
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31

July 21st

UAG: Warning, POST without Content-Type not Allowed

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;

UAG: Publishing VMWare View using Forefront Unified Access Gateway

Supported client OS: Windows XP 32bit and Windows Vista 32bit

July 8th

July 5th

UAG & DirectAccess: Some of my applications don’t work on DirectAccess, what should I do?

This is a very common situation which people might face when deploying Microsoft DirectAccess technology. Before going into how to work around this we need to know why the applications which work in internal network would fail to work on DirectAccess connectivity.

Let’s go through few types of applications and the reasons why they might fail to connect

Client/Server Applications

 

Copyright © 2024 Iron Networks, Inc. All Rights Reserved.