Local reply modification

    Features:

    Example of a LocalReplyConfig

    In above example, if the status_code is 400, it will be rewritten to 401, the response body will be rewritten to as “not allowed”.

    Local reply format modification

    The response body content type can be customized. If not specified, the content type is plain/text. There are two body_format fields; one is the body_format field in the message and the other body_format_override field in the mapper. The latter is only used when its mapper is matched. The former is used if there is no any matched mappers, or the matched mapper doesn’t have the body_format specified.

    Optionally, content-type can be modified further via field. If not specified, default content-type is text/plain for text_format and application/json for .

    Example of a LocalReplyConfig with body_format field.

    1. mappers:
    2. - filter:
    3.     status_code_filter:
    4.       comparison:
    5.         value:
    6.           default_value: 400
    7.           runtime_key: key_b
    8.   status_code: 401
    9.   body_format_override:
    10.     text_format: "<h1>%LOCAL_REPLY_BODY% %REQ(:path)%</h1>"
    11.     content_type: "text/html; charset=UTF-8"
    12. - filter:
    13.       comparison:
    14.         op: EQ
    16.           default_value: 500
    17.           runtime_key: key_b
    18.   status_code: 501
    19. body_format:
    20.   text_format: "%LOCAL_REPLY_BODY% %RESPONSE_CODE%"

    In above example, there is a body_format_override inside the first mapper with a filter matching status_code == 400. It generates the response body in plain text format by concatenating %LOCAL_REPLY_BODY% with the :path request header. It is only used when the first mapper is matched. There is a body_format at the bottom of the config and at the same level as field mappers. It is used when non of the mappers is matched or the matched mapper doesn’t have its own specified.