There were several issues here:
- The IChannelDispatcherBoundListener was defined twice, in two different namespaces, and it caused code in
ChannelDispatcher.Attach not to set its associated listener's ChannelDispatcher property to the correct value.
This, in turn, caused incorrect HttpListenerManagerTable operation, where it would put the "/js" and "/jsdebug"
dispatchers in separate HttpListenerManagers, instead of in the main (base) service's one.
- After fixing the above, it turned out that SvcHttpHandler selected the manager based on the host's base address,
when it should first try to find one whose URL matches the current request exactly.
SecurityTokenParameters.InitializeSecurityTokenRequirement() needs to become
protected internal, so changed all overrides as well.
Some implementation in WindowsStreamSecurityBindingElement is needed only for
NetTcpBinding implementation.
Had to disable a test in SymmetricSecurityBindingElement that depended on
OneWay support (which is not yet done).
SvcHttpHandler maintains a mapping of HttpContext to ManualResetEvent. Entries are
removed from the cache in EndHttpRequest. The code makes sure the context exists in
the cache before attempting to access it.
Pass the listener as it's own async state so that we avoid potential null derefs in the callback. Also wrap the BeginAccept and EndAccept calls in their own try/catches in case they throw an exception.
* System.ServiceModel.Channels/HttpRequestChannel.cs: For Moonlight use
the WebResponse.SupportsHeaders before accessing the Headers collection.
This is needed because (the default) browser stack does not expose the
headers from its responses. Fix bug #642193
* BinaryMessageEncoder.cs, MessageEncoder.cs:
The default content type value is null, not the ContentType value.
* HttpReplyChannel.cs : pass HTTP ContentType header value to
MessageEncoder.ReadMessage().
svn path=/trunk/mcs/; revision=160376
* Message.cs, MessageBufferImpl.cs, MessageImpl.cs: preserve and
output attributes prefixes, to copy Body/@wsu:Id to successfully
verify the xmldsig.
svn path=/trunk/mcs/; revision=160142
* MessageHeader.cs : to clone raw xml completely, avoid using
ReadOuterXml() and text reader but use XmlNodeReader instaed.
* Message.cs : avoid extraneous xmlns:u attribute.
svn path=/trunk/mcs/; revision=160120
* MessageImpl.cs : When XmlReaderMessage was writing its contents,
it was dropping body attributes, including wsu:Id for WS-Security.
svn path=/trunk/mcs/; revision=160105
* ChannelFactoryBase.cs : null via uri parameter is not allowed.
* ClientRuntimeChannel.cs : give non-null Via uri.
* HttpTransportBindingElementTest.cs : add test for
ChannelFactoryBase`1.CreateChannel() with null via uri.
svn path=/trunk/mcs/; revision=159934
* HttpStandaloneReplyChannel.cs, HttpChannelListenerEntry.cs,
HttpContextInfo.cs, HttpListenerManager.cs,
HttpStandaloneRequestContext.cs, HttpListenerManagerTable.cs:
Fixed wsdl support in the new codebase, so enabled it again, and
made significant changes for ASP.NET integration. Now ASP.NET
implementation switched to the new one.
* SvcHttpHandler.cs : add required code for new ASP.NET HTTP stack.
Support for new and old stack (both) are temporarily enabled.
* HttpTransportBindingElement.cs : switch to new ASP.NET stack.
svn path=/trunk/mcs/; revision=159907
* HttpStandaloneReplyChannel.cs, HttpStandaloneRequestContext.cs:
add more code that the asp.net stuff will become like.
* SvcHttpHandlerFactory.cs : remove unused code.
* SvcHttpHandler.cs : ditto. Add some code for what new asp.net
support will look like.
svn path=/trunk/mcs/; revision=159818
* Message.cs, MessageImpl.cs, MessageBufferImpl.cs : remove BodyId.
XML attributes on s:Body are handled appropriately, not limited to
wsu:Id. Added several required overrides to Message and
MessageBuffer implementation classes.
* SecureMessageGenerator.cs : so, don't use BodyId. Treat it as a
specific case but still fallback.
svn path=/trunk/mcs/; revision=159800