Fix issue #947

[0x1b5b]

Description

This pull request fixes issue #947. Since warcio appears to be lacking support for zstd at the moment, I have decided to remove zstd from the Accept-Encoding HTTP header's value. This is similar to the patch that was provided in pull request #444 as a solution to issue #434.

Motivation and Context

See issue #947.

Screenshots (if appropriate):

Compare this screenshot to the one provided in issue #947.

Types of changes

• Replay fix (fixes a replay specific issue)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added or updated tests to cover my changes. (I could not find existing tests for this code path, so I decided not to add any new tests.)
• All new and existing tests passed. (They do not seem to pass even without my changes.)

[ato]

I think this needs a comma:

Suggested change

	disallowed_encodings = ('zstd') if has_brotli else ('zstd', 'br')
	disallowed_encodings = ('zstd',) if has_brotli else ('zstd', 'br')

Otherwise if has_brotli is true, then disallowed_encodings is the string "zstd" not a tuple which means the not in disallowed_encodings is checking for any substring of 'zstd'.

>>> 'z' not in ('zstd')
False
>>> 'z' not in ('zstd',)
True

[wumpus]

Good catch