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
Copy file name to clipboardExpand all lines: docs/alb.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,7 +193,7 @@ This mechanism is useful in applications such as live internet television. Consi
193
193
194
194
#### Custom Good Status Codes List
195
195
196
-
By default, fgr will return the first response with a status code < 400. However, you can optionally provide an explicit list of good status codes using the `fgr_status_codes` configuration setting, as shown in the example below. When set, Trickster will return the first response to be returned that has a status code found in the configured list.
196
+
By default, fgr will return the first response with a status code < 400. However, you can optionally provide an explicit list of good status codes using the `fgr.status_codes` configuration setting, as shown in the example below. When set, Trickster will return the first response to be returned that has a status code found in the configured list.
197
197
198
198
#### First Good Response Configuration Example
199
199
@@ -216,10 +216,11 @@ backends:
216
216
provider: alb
217
217
alb:
218
218
mechanism: fgr # first good response
219
-
fgr_status_codes: [ 200, 201, 204 ] # only consider these codes when selecting a response
220
219
pool:
221
220
- node01
222
221
- node02
222
+
fgr:
223
+
status_codes: [ 200, 201, 204 ] # only consider these codes when selecting a response
223
224
```
224
225
225
226
Here is the visual representation of this configuration:
0 commit comments