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

'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 code I'm intended on sending is '503 Slow Down', as per:
http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html

It also needs to be wired up to the Lua function:
AppletHTTP.set_status(applet, code[, reason])
AppletHTTP.set_reason(applet, reason)

I'm willing to write up the code, just wondering if it should be a new
directive or an optional parameter.

--
Robin Hugh Johnson
E-Mail : robbat2@orbis-terrarum.net
Home Page : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ# : 30269588 or 41961639
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85