none
Deployng wcf service using WSDualHttpBinding into Azure RRS feed

  • Question


  • Hello All,

     

    I having some issues deploying a wcf service using WSDualHttpBinding into Azure.

    When I try to run my server and client locally with administrator rights everything run smoothly. I can deploy the server side on Azure App Service using publish in VisualStudio, I can access my service using : xxx. azurewebsites.net/ service.svc


    So everything looks good from the server side. But when I try to access my service using Azure App Service, it raise the following exception :

    “The content type text/html; charset=UTF-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were….”

     

    Using Fiddler, I look at the Xml response, and it looks like the webpage at xxx. azurewebsites.net /service.svc

    I’m really confuse where I am missing something, I’m new to WCF and Azure so any help would be really appreciated.

    PS : I can't post my configurations because my account is not yet validated so I can't post any link or image

    Best,
    vendredi 1 avril 2022 12:07

Toutes les réponses

  • Bonjour ,

    As this is a French forum I would kindly ask you to either translate your Post in French or to post it again on the English Forum:
    https://docs.microsoft.com/en-us/answers/index.html

    Merci d’avoir contacté les forums MSDN France. La langue utilisée sur ces forums est la langue Française. Donc, s’il vous plaît, modifiez votre premier message comme on vous demande dans l’étiquette sur les forums MSDN France.

    Merci pour votre compréhension et collaboration.

    Cordialement,
    Nina


    Microsoft propose ce service gratuitement, dans le but d'aider les utilisateurs et d'élargir les connaissances générales liées aux produits et technologies Microsoft. Ce contenu est fourni "tel quel" et il n'implique aucune responsabilité de la part de Microsoft.

    vendredi 1 avril 2022 14:24
    Modérateur