Expose HTTP response to end users

未关闭
#98 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
39/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
java
领域
api

调研方向

Start by reading the response handling and error reporting paths in the tus Java client, then review the three linked issues for related behavior. The request is to include response bodies in 4xx error messages and add an overridable TusClient callback for custom response handling; done means both behaviors are available to client users.

由索引模型根据 Issue 内容生成。

描述

enhancement

Is your feature request related to a problem? Please describe.

Users currently cannot retrieve the response body. This includes successful responses (e.g. after an upload is finished), but also error cases, where the error message only includes the status code. The response body is not included in the message, although it usually includes more details.

Describe the solution you'd like

  • Error messages from 4xx status codes should include the response body
  • TusClient should have a callback that can be override to handle the response object in a custom manner.

See https://github.com/tus/tus-java-client/issues/89, https://github.com/tus/tus-java-client/issues/59, https://github.com/tus/tus-java-client/issues/80, for example.

主要语言
Java
星标
246
派生
90
平均合并
13 小时 2 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

tus/tus-java-client 的其他 Issue

查看 tus/tus-java-client 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。