leanalcabasa
leanalcabasa
It was my error; forgot we had a network policy applied to the kubernetes. Adding the appropriate rules worked.
Actually, I can't seem to figure out the IP / Port to unblock. I tried it successfully by removing the network policy. Is there a document somewhere I can refer...
Hi @VitahaPo , I am also encountering the same issue. Can I ask if we have the same problem? After implementing the a pproach of https://github.com/CoreWCF/CoreWCF/discussions/853, it fixed the soap:address...
Thanks @VitahaPo I saw you commented another fix in your fork : https://github.com/VitahaPo/CoreWCF/commit/d12cf97f91b9a7c30375ae9998015efa04c3e6a3 Is it for a different problem? Hopefully, this PR gets approved so it is supported.
I see, thanks @VitahaPo Hi @mconnew , can we revisit this PR? It would be helpful for us that hosts it within AKS or behind a load balancer. Or maybe...
Found out that it is intended behavior. https://msdn.microsoft.com/en-us/library/hh779077.aspx