#dominoforever | Product Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Character encoding problems when posting to agent

Character encoding problems when posting to script agent, e.g. posting Danish characters like ÆØÅ

 

If I POST this JSON to a script agent

{

                             subject:"ÆØÅ"

}

 

Session.DocumentContext.REQUEST_CONTENT contains

{

subject:"ÆØÅ"

}

 

This isn’t very useful

 

Please do some basic character decoding or include charset support

  • Guest
  • Sep 20 2018
  • Under Consideration
  • Attach files
  • Guest commented
    7 May, 2021 07:40am

    Did a PMR: Case CS0218469
    "This use case is not supported, http post data is written in RAW form into the post data fields in the agent context note when running the agent, the data is not converted to LMBCS. Since the data is not in LMBCS the client and any other application notes application will not render the data correctly. Since the post data fields are text fields the lotus script agent will read the data as lmbcs when it is not lmbcs.

    This is day 1 behavior of Domino going back to version 4.6 and cannot be change because it would break many legacy agents. Recommended the customer encode the post data with base64 encoding the post data and have the agent convert decode/convert to lmbcs"

    Conclusion: YOu can 't build a standard REST / CRUD interface woth LotusScript in Domino. This is very disappointing

  • Admin
    Thomas Hampel commented
    10 Jan, 2020 09:40pm

    Moving this idea to product : Domino

  • Guest commented
    29 Oct, 2018 08:37am

    This is not a Domino Designer issue.

    It is the HTTP server that is parsing the POST request.

  • Admin
    Thomas Hampel commented
    27 Oct, 2018 07:47am

    Moving this idea to product : Domino Designer

  • Guest commented
    24 Sep, 2018 07:41am

    Domino fails even if an explicit HTTP request header is set on the POST request: Content-Type: application/json; charset=utf-8.

    This is unacceptable. UTF-8 is the default character set for JSON.

  • Guest commented
    23 Sep, 2018 10:01am

    Nope. Do not think I can? I am an independent consultant (not a partner or customer)

  • Admin
    Thomas Hampel commented
    23 Sep, 2018 09:44am

    Did you open a PMR for this problem?