ellzey/libevhtp — pull request #27 by ahochhaus (2011-12-30 20:38:55+00:00)
Title: evhtp_parse_query changes

* Allow > 1024 chars for keys and values.

* Automatically unescape keys and values using evhtp_unescape_string.
This changes functionality and could break existing code depending on the
assumptions of the calling code. If it is a desirable use-case to not
unescape keys and values I could expose an option (or an alternate API).
Please let me know your thoughts on this.

Is this type of functionality valuable upstream?

If so, can I do anything to improve the style/algorithm to prep for merge?

One downside that I noticed when using evhtp_unescape_string is that is it not easy to know the length of the resulting unescaped string. It might be nice at some point to expose that as a return value (i.e. -1 is failure; otherwise the len of the unescaped string is returned).