cancel
Showing results for 
Search instead for 
Did you mean: 

ASM Policy handling Emojis in JSON

Steve_Higgin
Nimbostratus
Nimbostratus

As part of one of our mobile apps there is a functionality to send a message to support, obviously in this day and age everyone likes to use emojis. This causes the ASM to block these messages as they are quite rightly classified as Malformed JSON data. Has anyone else come across this situation and how did you get around it, I do not want to turn inspection off of this value parameter as its free text it could contain anything? It could be done client side within the app to parse out any emojis, just wondering if there is anything that can be easily done on the ASM.

 

For reference, the payload is simple:-

 

{ "subject" : "subject text here", "message" : "message text here (this is where all the emojis appear 😊" }

 

3 REPLIES 3

ragunath154
Cirrus
Cirrus

i too had the similar violation,

based on tac reply i followed below settings  

 /usr/share/ts/bin/add_del_internal add relax_unicode_in_json 1

    bigstart restart asm

 

https://cdn.f5.com/product/bugtracker/ID476191.html

Steve_Higgin
Nimbostratus
Nimbostratus

Thanks for the reply, I will check this out.

spars
Altostratus
Altostratus

What's the risk associated with relaxing the unicode?