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
Like the title says, libtaxii currently can't handle gzipped responses (either Content-Encoding or Transfer-Encoding). This hasn't come up, because libtaxii doesn't specify gzip in the Accept-Encoding header.
Adding this feature will allow library users to specify gzip in the headers and not have to worry about getting an unparseable response back.
-Mark
The text was updated successfully, but these errors were encountered:
👍 for requests as well. It's really about development time to re architect clients.py, and whether we want to do a libtaxii 2.0 (I think there's other backward incompatible changes I'd like to make as well).
Like the title says, libtaxii currently can't handle gzipped responses (either Content-Encoding or Transfer-Encoding). This hasn't come up, because libtaxii doesn't specify gzip in the Accept-Encoding header.
Adding this feature will allow library users to specify gzip in the headers and not have to worry about getting an unparseable response back.
-Mark
The text was updated successfully, but these errors were encountered: