harababurel/gcsf

gzip compression

Open

#8 opened on Jun 27, 2018

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Rust (2,378 stars) (94 forks)user submission
enhancementgood first issuehelp wanted

Description

Google suggests enabling gzip compression before transferring files over the network:

In order to receive a gzip-encoded response you must do two things: Set an Accept-Encoding header, and modify your user agent to contain the string gzip. Here is an example of properly formed HTTP headers for enabling gzip compression:

Accept-Encoding: gzip
User-Agent: my program (gzip)

Find a way to enable this option in GCSF.

Contributor guide

Tech stack
rustrest api
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingHTTP compressionGCSF codebase structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the HTTP client implementation in GCSF, likely using reqwest or hyper. Look for where HTTP requests are built (e.g., in `src/google/drive.rs` or similar). Add an `Accept Encoding: gzip` header and modify the `User Agent` to include `gzip`. Ensure the response is properly decompressed. Check if the library automatically handles gzip; if not, add decompression logic. Verify with a Google Drive API call that responses are compressed.