I ran some tests with postman to see if these less than symbols were caused by FS or our application. we see that it is FS causing these character translations. My conclusion is that is an issue with FS as we are posting the device names as displayed to the API. I have seen these character translations when working with XML files.
< is the equivalent to <
> is the equivalent to >
<…> anything in between these character is removed, not equal to
Here are my test cases with calls directly to the FS API with Postman
I see that this forum takes the characters and translates them to the respective character symbol. Please see attached image
I understand from your post that, FS API is causing some unwanted translations. But to work with the team to solve this issue, I need your help with bit more information
Is it possible for you to let me know,
- What were you trying to accomplish?
- When and how does this translation happen?
- How is it affecting your app usual expectation?
What were you trying to accomplish?
We are creating an integration app that will import devices, applications, and relationships into Freshservice. We have a sync that utilizes the Freshservice API to get these assets into Freshservice
When and how does this translation happen?
The translation occurs during our sync which uses the Freshservice API . You can create an asset directly (using curl) along with a device name containing the characters I listed in this post and see the outcome of the translation.
How is it affecting your app usual expectation?
Though it is not common, if a device name contains these special characters it can be confusing to a customer when looking for their device.
We understand this is done to prevent HTML injection, as a resolution and expected outcome. translate both the
> characters, not just the
< as shown in the attached photo.
May I know which API are you trying to use in your app? I can get some help from the FS team. I see it has been quite some time, are you still facing this issue?
Hi @Saif, we are using freshservice https://api.freshservice.com/#create_asset
this is not affecting the functionality of our application but is something we though thought we should bring up as an edge case for testing. No further action needed.