mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-08-10 00:57:02 +02:00
Code Issues Projects Releases Wiki Activity

DOC: configuration: Unindent non-code sentences in the protobuf example

Browse Source 
Unindent to make the explanation go back to text from code formatted
example in tyhe HTMLized version. Still it's not perfect since these
are not haproxy examples but protobuf config, but... way better.
This commit is contained in:
Peter Gervai 2020-06-11 18:05:11 +02:00 committed by Willy Tarreau
parent f49a6049b8
commit df4c9d2a28
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/configuration.txt
View File

@ -15459,30 +15459,30 @@ ungrpc(<field_number>,[<field_type>])
PPoint hi = 49; PPoint hi = 49;
} }
let's say a body request is made of a "Rectangle" object value (two PPoint let's say a body request is made of a "Rectangle" object value (two PPoint
protocol buffers messages), the four protocol buffers fields could be protocol buffers messages), the four protocol buffers fields could be
extracted with these "ungrpc" directives: extracted with these "ungrpc" directives:
req.body,ungrpc(48.59.1,int32) # "latitude" of "lo" first PPoint req.body,ungrpc(48.59.1,int32) # "latitude" of "lo" first PPoint
req.body,ungrpc(48.59.2,int32) # "longitude" of "lo" first PPoint req.body,ungrpc(48.59.2,int32) # "longitude" of "lo" first PPoint
req.body,ungrpc(49.59.1,int32) # "latitude" of "hi" second PPoint req.body,ungrpc(49.59.1,int32) # "latitude" of "hi" second PPoint
req.body,ungrpc(49.59.2,int32) # "longitude" of "hi" second PPoint req.body,ungrpc(49.59.2,int32) # "longitude" of "hi" second PPoint
We could also extract the intermediary 48.59 field as a binary sample as follows: We could also extract the intermediary 48.59 field as a binary sample as follows:
req.body,ungrpc(48.59) req.body,ungrpc(48.59)
As a gRPC message is always made of a gRPC header followed by protocol buffers As a gRPC message is always made of a gRPC header followed by protocol buffers
messages, in the previous example the "latitude" of "lo" first PPoint messages, in the previous example the "latitude" of "lo" first PPoint
could be extracted with these equivalent directives: could be extracted with these equivalent directives:
req.body,ungrpc(48.59),protobuf(1,int32) req.body,ungrpc(48.59),protobuf(1,int32)
req.body,ungrpc(48),protobuf(59.1,int32) req.body,ungrpc(48),protobuf(59.1,int32)
req.body,ungrpc(48),protobuf(59),protobuf(1,int32) req.body,ungrpc(48),protobuf(59),protobuf(1,int32)
Note that the first convert must be "ungrpc", the remaining ones must be Note that the first convert must be "ungrpc", the remaining ones must be
"protobuf" and only the last one may have or not a second argument to "protobuf" and only the last one may have or not a second argument to
interpret the previous binary sample. interpret the previous binary sample.
unset-var(<var name>) unset-var(<var name>)