You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone. My team has noticed that there are tests around compression for the awsJson1_0 and awsJson1_1 protocols that are inconsistent with the specification.
These tests exercise gzip encoding in the context when the user has the possibility of providing a custom encoding via a member of the structure input annotated with @httpHeader("Content-Encoding).
However, the corresponding protocol specification makes it quite clear that http-binding traits must be ignored
Can you elaborate on whether the specification or the test is correct ?
The text was updated successfully, but these errors were encountered:
Hi everyone. My team has noticed that there are tests around compression for the
awsJson1_0
andawsJson1_1
protocols that are inconsistent with the specification.These tests exercise gzip encoding in the context when the user has the possibility of providing a custom encoding via a member of the structure input annotated with
@httpHeader("Content-Encoding)
.However, the corresponding protocol specification makes it quite clear that http-binding traits must be ignored
Can you elaborate on whether the specification or the test is correct ?
The text was updated successfully, but these errors were encountered: