Message263491
If this bug is to be moved forward, we should consider this:
The RFC 3986 defines that a query can have any of these characters:
/?:@-._~!$&'()*+,;= ALPHA DIGIT %HH (encoded octet)
But does not define how the data should be interpreted, leaving that to the naming authority and the URI schema (although http/https doesn't specify it as well; see RFC 7230).
OTOH, parse_qs (both on 2.x and 3.x) is very specific that the query string is of type application/x-www-form-urlencoded; which defines that the name is separated from the value by '=' and name/value pairs are separated from each other by '&', although the use of ';' to separate the pairs is only suggested to be supported by HTTP server implementors.
It could be that adding support to the characters specified by RFC 3986 pose as a challenge since there is no fixed schema and they can be freely used by the naming authority so perhaps we could add a parameter to enable/disable ';' as a pair separator? |
|
Date |
User |
Action |
Args |
2016-04-15 13:09:52 | luiz.poleto | set | recipients:
+ luiz.poleto, orsenthil, r.david.murray, ruben.orduz |
2016-04-15 13:09:52 | luiz.poleto | set | messageid: <1460725792.7.0.827381077499.issue20116@psf.upfronthosting.co.za> |
2016-04-15 13:09:52 | luiz.poleto | link | issue20116 messages |
2016-04-15 13:09:52 | luiz.poleto | create | |
|