Interop Scenario Fails with .Net4.0-rc1 : The server sent HTTP status code 400: Bad Request

Scenario
========
Interop Scenario 1 - Client_SUN STS_MS Server_MS

Setup
=====
metro 2.0.1
glassfish v3

Error Log
===========
---[HTTP response -
[https://ejp5359-vm1.india.sun.com:443/Security_Federation_FederatedService_Indigo/Symmetric.svc/Scenario_1_IssuedTokenOverTransport_UsernameOverTransport](https://ejp5359-vm1.india.sun.com:443/Security_Federation_FederatedService_Indigo/Symmetric.svc/Scenario_1_IssuedTokenOverTransport_UsernameOverTransport)

* 400]---
null: HTTP/1.1 400 Bad Request
Content-length: 0
X-powered-by: ASP.NET
Server: Microsoft-IIS/7.0
Date: Wed, 17 Mar 2010 14:06:13 GMT
--------------------
==========================================================
../../../interop/logs/run_log/scenario1-m-m-output.txt
com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status code
400: Bad Request
at
com.sun.xml.ws.transport.http.client.HttpTransportPipe.checkStatusCode(HttpTransportPipe.java:213)
at
com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:179)
at
com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:93)
at
com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:133)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:629)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:588)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:573)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:470)
at com.sun.xml.ws.client.Stub.process(Stub.java:319)
at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:157)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:109)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:140)
at $Proxy49.ping(Unknown Source)
at simple.client.PingServiceClientMS.main(PingServiceClientMS.java:60)
#### Environment
Operating System: All
Platform: All
#### Affected Versions
[2.0]

Source: [https://github.com/javaee/metro-wsit/issues/1379](https://github.com/javaee/metro-wsit/issues/1379)
Author: glassfishrobot

Start by reviewing the interop scenario and its output at ../../../interop/logs/run_log/scenario1-m-m-output.txt, then inspect the failing call at simple.client.PingServiceClientMS.java:60 and the HTTP status handling in HttpTransportPipe. Reproduce Scenario 1 with Metro 2.0.1 and GlassFish v3; done means the request no longer receives HTTP 400.

Written by the indexing model from the issue text.