In this particular case, the non-ascii character is blowing up as a side-effect of how the glance v1 API represents meta-data as HTTP headers.
This should be resolved with the v2 API where the meta-data is promoted up to the entity-body.
In this particular case, the non-ascii character is blowing up as a side-effect of how the glance v1 API represents meta-data as HTTP headers.
This should be resolved with the v2 API where the meta-data is promoted up to the entity-body.