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.