Willy,
On 4/20/21 8:40 PM, Willy Tarreau wrote:
I perfectly understand that some transformations may require the whole
URI for various reasons, but for those that could be expressed on
individual parts, I do think that converters will be way more flexible
over the long term.
Luckily this should be easy enough with the clear split between the action
and the actual normalizers that simply take an ist.
OK, great!
I forgot to issue dev17 last Friday, different work place, change of
habits and being busy on the pools mess made me simply forget it. I'll
do it for next Friday with some other stuff. If you think there's
anything doable by then, just let me know so that I can wait for you,
otherwise no stress, it can come at any time.
I don't plan on adding sample converters for normalization in 2.4. I
think the feature should first get some basic exposure based off the
http-request normalize-uri action and then we can look into extensions
once feature requests arrive. One bite at a time!
The only thing I will do before the final 2.4 release is adding a few
more normalizers for use within the http-request normalize-uri action.
Most notable the percent decoder for unreserved characters (%61dmin ->
admin) still is missing, due to its higher complexity compared to the
existing ones.
Best regards
Tim Düsterhus
