This bug is obviously not related to Fuel, but is clearly a bug of glance v1 API.
RFC2616 States the following
https://tools.ietf.org/html/rfc2616#section-4.2
CHAR = <any US-ASCII character (octets 0 - 127)> ... token = 1*<any CHAR except CTLs or separators> separators = "(" | ")" | "<" | ">" | "@" | "," | ";" | ":" | "\" | <"> | "/" | "[" | "]" | "?" | "=" | "{" | "}" | SP | HT .... message-header = field-name ":" [ field-value ] field-name = token
Thus, it means, that the response headers for custom fields MUST be URL encoded and decoded on the client side. Or this particular feature should be mentioned in the documentation. In any case this is an invalid bug for Fuel
This bug is obviously not related to Fuel, but is clearly a bug of glance v1 API.
RFC2616 States the following
https:/ /tools. ietf.org/ html/rfc2616# section- 4.2
CHAR = <any US-ASCII character (octets 0 - 127)>
| "," | ";" | ":" | "\" | <">
| "/" | "[" | "]" | "?" | "="
| "{" | "}" | SP | HT
message- header = field-name ":" [ field-value ]
...
token = 1*<any CHAR except CTLs or separators>
separators = "(" | ")" | "<" | ">" | "@"
....
field-name = token
Thus, it means, that the response headers for custom fields MUST be URL encoded and decoded on the client side. Or this particular feature should be mentioned in the documentation. In any case this is an invalid bug for Fuel