Hoverfly Cloud
Visit Our Main SitePricingTry Hoverfly Cloud
  • Introduction
  • Use cases for API Simulation
  • Key concepts
  • What's New
  • Dashboard
  • Simulation
    • Create simulations
    • Configuring Request Matchers
      • JSON Request Matchers on the Body
        • EXACT Matcher
        • JSON Matcher
        • JSON Partial Matcher
        • JSONPath Matcher
        • Regular Expression Matcher
      • Handling the response when Hoverfly cannot match
    • Building a JSON Response
      • Using a JSON object from the Request
      • Looping over a JSON array from the Request
    • Simulating Webhooks and Callbacks
    • Using templating in simulations
      • Render back any part of the Request
      • Render synthetic data
      • Faker functions
      • Render dates and times with offsets
      • Conditional logic
      • Looping over arrays
      • Variables and Arrays
      • Arithmetic operations
      • String operations
      • Validation operations
      • Simulating a persistent backend
      • Transitioning state between requests
      • Combining and nesting templating functions
      • Useful helper functions
      • Avoiding HTML encoding in function return values
    • Using data sources in simulations
      • Querying data sources
      • Updating data in data sources
      • Deleting data from data sources
      • Inserting data into a data source
      • Guidance on using the SQL like syntax
    • Working with Simulation Files
  • Service
    • Start a new service
    • Use a service
    • Update a service
    • Configuring Journal Indexing
  • Command line interface
    • Hoverfly Cloud CLI commands
  • Tutorials
    • Quickstart
    • Creating simulations and services
      • Tutorial 1: Create a service and simulation manually
      • Tutorial 2: Create a service and simulation by importing from a Swagger specification
      • Tutorial 3: Create a service and simulation by capturing real API traffic
    • Response Templating
      • Tutorial 4: Response Templating
    • Hoverfly service modes
      • Tutorial 5: Simulate, Capture, Spy and Passthrough modes
    • Automating with the CLI and API
      • Tutorial 6: Using the CLI and the Hoverfly Cloud API
Powered by GitBook
On this page
  1. Simulation
  2. Using templating in simulations

Avoiding HTML encoding in function return values

Prevent HTML encoding of function return values in Hoverfly Cloud templating to ensure correct formatting in your API responses.

By default the handlebars engine will HTML escape every value it returns into the template.

What this means is that if the value returned from any function contains one of the HTML special characters, then they will be replaced with their escaped equivalent.

Character
Description
Escaped Equivalent

&

Ampersand

&

<

Less than

&lt;

>

Greater than

&gt;

"

Double quote

&quot;

'

Single quote

&apos; or &#39;

©

Copyright symbol

&copy;

®

Registered symbol

&reg;

™

Trademark symbol

&trade;

In order to avoid this behavior, you need to enclose the function in triple handlebar syntax.

for example:

{{faker 'Question'}} 

might return

You probably haven&apos;t heard of them?

where as, if used with triple handlebars:

{{{faker 'Question'}}} 

might return

You probably haven't heard of them?
PreviousUseful helper functionsNextUsing data sources in simulations

Last updated 3 months ago