ipfs/kubo

PUT existing file with Writeable Gateway not returning expected result.

Open

#3,923 创建于 2017年5月13日

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

描述

Version information:

go-ipfs version: 0.4.8- Repo version: 5 System version: amd64/linux Golang version: go1.8

Type:

Bug

Severity:

Medium

Description:

When using a writeable HTTP gateway:

  • If I PUT to a directory tree for a path that doesn't exist in the tree, the gateway returns the expected result: the ipfs-hash for an edited directory tree that contains the uploaded file at the specified path.
  • However, if I PUT to a directory tree for a path that already exists in the tree, I instead get back the ipfs-hash for the file I uploaded- as if I had used the POST interface.
  • I would expect, in that case, to receive the ipfs-hash of the root of an edited directory tree that contains the uploaded file in place of the path's former content.

贡献者指南

技术栈
go
领域
backendapi
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic understanding of IPFSFamiliarity with GoKnowledge of HTTP PUT semantics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
Investigate the writeable HTTP gateway implementation in the kubo repository, specifically the PUT handler. The bug report indicates that PUT on an existing path returns the hash of the uploaded file instead of the hash of the updated directory tree. Look at the gateway code, likely in 'core/commands/' or 'gateway/' directories, and check how path resolution and file replacement are handled. The expected behavior is to return the root hash of the directory tree after replacing the file. Compare with the POST behavior to identify the discrepancy.
PUT existing file with Writeable Gateway not returning expected result. · ipfs/kubo#3923 | Good First Issue