parse_query() rejects 'valid' query strings

[rcane]

Although a query string usually contains key value pairs, it is perfectly legal to have a query like this:

http://example.com/api/foo?1234

This is used for example to implement tracking beacons. The current parse_query() implementation throws an exception given this query. I am not sure how to fix this. parse_query returns a map of key value pairs. So it cannot deal with this in its current form. In my particular use case I would simply like to ignore such queries. So maybe there could be an option for parse_query similar to express_router_t::http_get's option to enable strict parse rules.

Another potential problem with parse_query is that it only accepts & as a separator. But W3C also recommends that servers support semicolon separators.

[eao197]

Thanks for reporting this! It requires some time to think... I'll take a timeout (hope it'll be short).

[eao197]

The master branch now contains an updated version. This version:

• allows usage of ; as a separator in query string;
• has a new method query_string_params_t::tag() that returns optional_t<string_view_t>. For a query like http://example.com/api/foo?1234 it'll return 1234;
• parse_query now handles tag (web beacon, tracing beacon) in query strings.

[rcane]

Thanks for the quick update. This fixes my problem.