Posted on: 5/8/2013 9:47:44 PM | Views : 406

We have a WIF FAM/SAM module configured for use with our third party ASP.NET 3.51 web app.   The WIF 3.51 FAM module is supposed to receive a HTTP POST of a SAML token and go from there.   Unforunately, something is preventing use of HTTP POST verb unless I enable RAMMFAR for the IIS modules (FAM/SAM) in web.config.
Here is the request/response:

POST http://foo.acme.com/capture/ HTTP/1.1 Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-shockwave-flash, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */* Accept-Language: en-us User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E) Content-Type: application/x-www-form-urlencoded Accept-Encoding: gzip, deflate Host: foo.acme.com Content-Length: 9390 Connection: Keep-Alive ...

Go to the complete details ...