You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 5, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/targets/http.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Create an instance of the HTTP Target at TriggerMesh as part of a Bridge.
27
27
-`Password` when using basic authentication needs to reference the aforementioned password secret.
28
28
-`Headers` is a set of key/value pairs that will be set withing the HTTP request.
29
29
30
-
Save the target, fill the rest of the bridge components and press `Submit Bridge`.
30
+
Save the target, fill the rest of the bridge components, and press `Submit Bridge`.
31
31
32
32
## Trigger Configuration
33
33
@@ -41,20 +41,20 @@ As an example:
41
41
- HTTP Target is interested in events whose type is `calendar.pto.request`.
42
42
- The response from workday will generate a CloudEvent type `workday.pto.response` and source `workday.instance1`
43
43
44
-
Trigger should be configured to avoid feeding these responses into the HTTP Target, a filter key `type` and value `calendar.pto.request` would provide such protection
44
+
Trigger should be configured to avoid feeding these responses into the HTTP Target. A filter key `type` and value `calendar.pto.request` would provide such protection.
45
45
46
46
## Events Types
47
47
48
48
The HTTP Target expects a cloud event request that complements the Target configured values.
49
49
50
-
There is no requirement regarding the type header value, any cloud event containing the expected data is valid to process. Data needs to be a JSON structure that might contain these optional fields:
50
+
There is no requirement regarding the type header value. Any cloud event containing the expected data is valid to process. Data needs to be a JSON structure that might contain these optional fields:
51
51
52
52
53
-
| Field | Description | Example|
54
-
|--- |--- |---|
55
-
| query_string | Key/value pairs formatted as query string |`name=jane&lastname=doe`|
56
-
| path_suffix | Will be appended to the target's path |`apparel/tshirts`|
57
-
| body | String to be set as the request body |`{\"size\":\"L\",\"color\":\"beige\"}`|
53
+
| Field | Description | Example |
54
+
|--- |--- |--- |
55
+
| query_string | Key/value pairs formatted as query string |`name=jane&lastname=doe`|
56
+
| path_suffix | Will be appended to the target's path |`apparel/tshirts`|
57
+
| body | String to be set as the request body |`{\"size\":\"L\",\"color\":\"beige\"}`|
0 commit comments