From: Thayne McCombs <astrotha...@gmail.com>
Add some documentation on how to handle percent encoded characters in
input to the param() converter.
---
doc/configuration.txt | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/doc/configuration.txt b/doc/configuration.txt
index d9f47c2eb..9505fc71d 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -17423,12 +17423,19 @@ param(<name>,[<delim>])
an alternative to `urlp(<name>)` which only uses "&" as a delimiter, whereas
urlp
also uses "?" and ";".
+ Note that this converter doesn't do anything special with url encoded
characters. If
+ you want to decode the value, you can use the url_dec converter on the
output. If
+ the name of the paramater in the input might contain encoded characters,
you'll probably
+ want do normalize the input before calling param. This can be done using
+ "http-request normalize-uri", in particular the percent-decode-unreserved and
+ percent-to-uppercase options.
+
Example :
str(a=b&c=d&a=r),param(a) # b
str(a&b=c),param(a) # ""
str(a=&b&c=a),param(b) # ""
str(a=1;b=2;c=4),param(b,;) # 2
- query,param(redirect_uri)
+ query,param(redirect_uri),urldec()
protobuf(<field_number>,[<field_type>])
This extracts the protocol buffers message field in raw mode of an input
binary
--
2.36.1
