[UDA2.0] Control point must include "identity" encoding if Accept-Encoding is used
Submitted by Jussi Kukkonen
Assigned to GUPnP Maintainers
Another meaningless deviance from HTTP proper (device architecture reference 2.1):
Accept-Encoding Allowed.Specified by RFC2616 section 14.3. Allowed encoding are identitiy, compress and gzip. The identity encoding shall be present and without value q=0. When the request is satisfied by the Server, then the content-encoding header shall be present. The value of the content_encoding header specifies the used encoding type of the response. Used values are vendor specific.
So "identity" must be present if the header is used -- unlike HTTP where identity is assumed by default. Apparently the test tools now fail if "identity" is not there.
I've not tested whether libsoup does something magic here or if we can just add something like "Accept-Encoding: gzip, identity;q=0.1" to every request we make.