| commit | 3d9dd93a1452e28c728483b03e352691238491ed | |
| author | Joshua Oreman <oremanj@rwcr.net> | |
| Wed, 30 Dec 2009 03:36:04 +0000 (29 22:36 -0500) | ||
| committer | Marty Connor <mdc@etherboot.org> | |
| Wed, 20 Jan 2010 23:14:28 +0000 (20 18:14 -0500) | ||
| tree | 73a41396fd514d12dbd7bd69ebfc49810bf73c7c | treesnapshot (tar.gz zip) |
| parent | ef9d1a32c6dc83d1086141c18d2be19a05ab8e49 | commitdiff |
[uri] Decode/encode URIs when parsing/unparsing
Currently, handling of URI escapes is ad-hoc; escaped strings are
stored as-is in the URI structure, and it is up to the individual
protocol to unescape as necessary. This is error-prone and expensive
in terms of code size. Modify this behavior by unescaping in
parse_uri() and escaping in unparse_uri() those fields that typically
handle URI escapes (hostname, user, password, path, query, fragment),
and allowing unparse_uri() to accept a subset of fields to print so
it can be easily used to generate e.g. the escaped HTTP path?query
request.
Signed-off-by: Joshua Oreman <oremanj@rwcr.net>
Signed-off-by: Marty Connor <mdc@etherboot.org>
Currently, handling of URI escapes is ad-hoc; escaped strings are
stored as-is in the URI structure, and it is up to the individual
protocol to unescape as necessary. This is error-prone and expensive
in terms of code size. Modify this behavior by unescaping in
parse_uri() and escaping in unparse_uri() those fields that typically
handle URI escapes (hostname, user, password, path, query, fragment),
and allowing unparse_uri() to accept a subset of fields to print so
it can be easily used to generate e.g. the escaped HTTP path?query
request.
Signed-off-by: Joshua Oreman <oremanj@rwcr.net>
Signed-off-by: Marty Connor <mdc@etherboot.org>