Comments on: 502 (Bad Gateway) and Http clients

By: BizTalk, WCF and the Bad Gateway « Santosh Benjamin’s Weblog

BizTalk, WCF and the Bad Gateway « Santosh Benjamin’s Weblog — Sat, 28 Nov 2009 16:52:38 +0000

[...] buried deep in the bindings that caused us the grief. After sorting this out I stumbled across this post from Kenny Wolf which points to the offending setting. Wish I had found that earlier, but then I wouldnt have [...]

By: Kenny

Kenny — Fri, 09 Mar 2007 02:11:40 +0000

What account are each of these applications running as? It sounds like the domain account for the windows service does not have the correct proxy settings

By: Harvinder Bholowasia

Harvinder Bholowasia — Sat, 24 Feb 2007 11:04:10 +0000

I am trying to get the Metadata of a service using MetadataExchangeClient, from a Self-Hosted (Windows Service) WCF service. I am getting the following error:-
System.InvalidOperationException was caught
Message=”Metadata contains a reference that cannot be resolved: ‘http://harvinder-test.csfidc.com/Session40/SessionManagerAdmin.svc?xsd=xsd1′.”
Source=”System.ServiceModel”
StackTrace:
at System.ServiceModel.Description.MetadataExchangeClient.MetadataRetriever.Retrieve(TimeoutHelper timeoutHelper)
at System.ServiceModel.Description.MetadataExchangeClient.ResolveNext(ResolveCallState resolveCallState)
at System.ServiceModel.Description.MetadataExchangeClient.ResolveNext(ResolveCallState resolveCallState)
at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(MetadataRetriever retriever)
at System.ServiceModel.Description.MetadataExchangeClient.GetMetadata(Uri address, MetadataExchangeClientMode mode)
at Microsoft.ConnectedServices.MV.DebugService.SessionChannelFactory._getKerberosEndpoint(String server) in C:\MVInstall\Local\src\MVServer\Microsoft.ConnectedServices.MV.DebugService\SessionChannelFactory.cs:line 107

The inner-exception is The remote server returned an error: (502) Bad Gateway.

The code that I used to get the Metadata is:-
private static ServiceEndpoint _getKerberosEndpoint(string server)
{
string ssuffix = System.Configuration.ConfigurationManager.AppSettings["SessionManagerAdminAddressSuffix"];
WSHttpBinding mexBinding = new WSHttpBinding(SecurityMode.None);
mexBinding.MaxReceivedMessageSize = Int32.MaxValue;
MetadataExchangeClient mexClient = new MetadataExchangeClient(mexBinding);
mexClient.ResolveMetadataReferences = true;
MetadataSet metadataSet = null;
WsdlImporter importer = null;
ServiceEndpoint endpointToReturn = null;

//Get the ISessionMgrAdmin Metadata
Uri wsdlUri = new Uri(“http://” + server + “/” + ssuffix + “?wsdl”);
metadataSet = mexClient.GetMetadata(wsdlUri, MetadataExchangeClientMode.HttpGet);
importer = new WsdlImporter(metadataSet);
ServiceEndpointCollection secCollection = importer.ImportAllEndpoints();

WSHttpBinding currentBinding = null;
foreach (ServiceEndpoint ep in secCollection)
{
currentBinding = ep.Binding as WSHttpBinding;
if (currentBinding == null || currentBinding.Security.Message.ClientCredentialType != MessageCredentialType.Windows)
continue;
endpointToReturn = ep;
break;
}

return endpointToReturn;
}

But when I try to get the Metadata of the same service, using a ConsoleApplication (using the same piece of code, as in the Windows Service) â€“ I am able to retrieve the ServiceEndpoint correctly!!
Can someone please tell me what might be going wrong?

By: mattonsoftware.com : .NET Resources

mattonsoftware.com : .NET Resources — Sat, 06 May 2006 08:33:34 +0000

[...] [...]

By: kennyw.com » Blog Archive » Configuration Http Proxies in WCF

kennyw.com » Blog Archive » Configuration Http Proxies in WCF — Thu, 20 Apr 2006 23:41:02 +0000

[...] When using Http, proxy configuration madness is a fact of life. If misconfigured, you can wind up trying to decipher obtuse 502 (Bad Gateway) and 504 (Gateway Timeout) errors. [...]

By: Hao Xu

Hao Xu — Tue, 25 Oct 2005 22:59:29 +0000

502 can also be due to the firewall if the server is running on the same machine. If the on-machine server is listening at a port blocked by the firewall, the proxy server won’t be able to connect. It will ultimately time out after several failed TCP SYN packets and return 502 to client.

By: Yasser Shohoud

Yasser Shohoud — Wed, 12 Oct 2005 17:43:13 +0000

Meet the WCF Channel Model – Part 1

For the past 5 months or so, Iâ€™ve been working on the WCF Core Communications team (with Kenny, Matt,…