Add headers to body
Use extractors to capture request header values and add those values to the request body.
The following example shows you how to use extractors to extract request header values by using regular expressions. The captured header values are then added to the response body by using the MergeExtractorsToBody setting. You can also use the extractors to indicate where you want to place the request header values in the body.
This guide uses a subset of the supported transformation template attributes. To review all the attributes that you can set, see Templating language.
Before you begin
Follow the Get started guide to install Gloo Gateway.
Follow the Sample app guide to create a gateway proxy with an HTTP listener and deploy the httpbin sample app.
Get the external address of the gateway and save it in an environment variable.
Add header values to the response body
Create a JSON file that you use as the body for your request.
cat << EOF > data.json { "payload": { "foo": "bar" } } EOFCreate a GlooTrafficPolicy with the following transformation rules:
- You extract the
rootandnestedrequest headers by using a regular expression that captures the entire value of the header. You save the extracted values in therootandpayload.nestedextractors. - The dot notation that you use for the extractor names determines the placement of the header in the body. For example, if no dot notation is used, such as in
root, the header is added to the body’s root level. If dot notation is used, such as inpayload.nested, the extractor is added under thepayload.nestedfield. - The
MergeExtractorsToBodysetting is used to automatically add all the extractors to the body.
kubectl apply -f- <<EOF apiVersion: gloo.solo.io/v1alpha1 kind: GlooTrafficPolicy metadata: name: transformation namespace: httpbin spec: targetRefs: - group: gateway.networking.k8s.io kind: HTTPRoute name: httpbin glooTransformation: stages: early: requests: - transformation: template: extractors: # The name of this attribute determines where the value will be nested in the body. # Because no dots are specified, such as root.nested, the root header value is added to the body's root level. root: # Name of the header to extract. header: 'root' # Regex to apply to the header. This value is required and is configured to capture the entire header. regex: '.*' # The name of this attribute determines where the value will be nested in the body. # Because dot notation is used, the nested header is placed under the placeholder.nested field in the body. payload.nested: # Name of the header to extract header: 'nested' # Regex to apply to it. This value is required and is configured to capture the entire header. regex: '.*' # Merge all extractors to the body. bodyTransformation: type: MergeExtractorsToBody EOF- You extract the
Send a request to the httpbin app and include the
rootandnestedrequest headers. Verify that you get back a 200 HTTP response code and that the value of therootheader is added to the body’s root level, and that thenestedheader value is added under thepayload.nestedfield in your response.Example output:
... "json": { "payload": { "foo": "bar", "nested": "nested-val" }, "root": "root-val" }
Cleanup
You can remove the resources that you created in this guide.
kubectl delete glootrafficpolicy transformation -n httpbin