ipfs/kubo

Compressed response from server

Open

#4,385 创建于 2017年11月13日

在 GitHub 查看
 (3 评论) (3 反应) (0 负责人)Go (13,906 star) (2,725 fork)batch import
help wantedkind/enhancement

描述

Version information:

go-ipfs version: 0.4.11- Repo version: 6 System version: amd64/windows Golang version: go1.9

Type: Enhancement

Description:

Compressing the response from the server can lower bandwidth requirements, especially when transferring large blocks.

The HTTP header Accept-Encoding: gzip should be accepted in a request. The server should then send a compressed response with Content-Encoding: gzip

贡献者指南

技术栈
go
领域
backendapi
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Go programmingHTTP protocolgzip compression
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Look at the HTTP gateway handler in the go ipfs codebase, specifically in the 'core/http' or 'cmd/ipfs' directories. The issue requests adding support for Accept Encoding: gzip and responding with Content Encoding: gzip. A common approach is to use a middleware that wraps the response writer with gzip compression. Check if there are existing middlewares or a way to plug in compression. The implementation should be server wide or configurable. Review any linked PRs or comments for additional context.