[RFC] Setting custom reasons with http-response: optional param vs new directive

'rsprep' allows modification of the reason text, for custom status reasons. 'http-response set-status' however just uses the hard-coded reason for each status code. Should set-status get an additional optional second parameter of a string, or should we add a set-reason directive instead? The cod

Reg

-- *Best Regards* *Lapuinka*