importer: Fix parsing gzipped content on invalid Content-Type header
RIPE seems to have misconfigured their webserver which now sends
application/octet-stream for all gzipped files instead of
application/x-gzip or similar which is what the importer would expect.
Instead of only checking the content type, we will now test whether we
see the gzip magic and try to decompress the file then.
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Showing
Please register or sign in to comment