Layer 7 API Management

Expand all | Collapse all

French Character issue

Jump to Best Answer
  • 1.  French Character issue

    Posted 11-22-2017 02:25 PM

    French character issue

  • 2.  Re: French Character issue

    Posted 11-22-2017 03:49 PM

    Would you be able to expand on what the issue is? The short text provided does not provide enough guidance to help out. We will need to know the product, version of the product, what you are attempting to do, any errors, etc.




    Stephen Hughes

    Director, CA Support

  • 3.  Re: French Character issue

    Posted 11-30-2017 04:13 PM

    Hi Durairaj

    Just wanted to see if you can provide more details on the issue you are having please.



  • 4.  Re: French Character issue

    Posted 11-30-2017 04:22 PM



    We are getting the corrupted French Character issue while receiving the response from Supplier into Layer7 Gateway. The same supplier response works if called directly.



    Thanks & Regards,


  • 5.  Re: French Character issue

    Posted 12-01-2017 12:33 PM

    Hi krishnamurthy.durairaj,


    Can you elaborate a bit?

    Are you receiving an error? If so, what is the exact message?


    Or is it actually character corruption, meaning the response is intended to be 'bienvenue à soutenir' but returns something like this as п╥я▐п╠я─я▀ ?


    Can you also describe the flow a bit more, are you using an HTTP route assertion to the supplier? 302 redirects? If we could get a sample of the actual request/response intended it would be helpful.




  • 6.  Re: French Character issue

    Posted 12-01-2017 01:02 PM

    We dont get an error but when receiving the French Content Response from the Expedia Supplier we are getting the improper French accent for eg we are getting "établissement" instead of établissement. Basically the frenc character é is getting splitted to é

  • 7.  Re: French Character issue
    Best Answer

    Posted 12-03-2017 05:31 PM

    Hi krishnamurthy.durairaj ,

    I assume that you're using route via http assertion to call the Expedia Supplier, you may add audit details assertion just after the route via http assertion, and show the content-type of the response using context variable ${response.http.allheadervalues}


    The content-type header should look like,



    You can check if the charset of the content-type is set properly.

    If the charset is not correct, you may,

    1. ask Expedia Supplier to return correct content-type


    2. use Validate or Change Content Type assertion to change the content-type of response (put it after route via http assertion)