Hi,
I commented on issue #77 (
https://code.google.com/p/rest-assured/issues/detail?id=77), and would be happy to submit a pull request, but it's unclear to me how best to handle this.
First, the problem I'm trying to solve:
I'm using REST-Assured to test against a Jersey/Jetty-based service and verify ETags in different situations. It turns out that when the Accept-Header has 'gzip', the server will compress the body and modify the ETag by appending -gzip to it. This means we have to manually remove the -gzip from the returned ETag in order to test that it's the ETag we expect. This is a pain.
It looks like the ContentEncoding class is intercepting and always adding 'gzip, deflate' to the Accept-Header in the Request. I can't see a way to change this via any of the configuration classes (seems like it could be part of the EncoderConfig?).
Any suggestions?
Thanks,
;ted
--