Skip to content

Unable to open minio's pre-signed URL Error response: statusCode:400 #3138

Open
@faithererer

Description

@faithererer

This issue is unique.

  • I have used the search tool and did not find an issue describing my bug.

Operating System of DocumentServer

Docker

Version information

docker-lastest

Expected Behavior

[2025-02-24T07:59:19.327] [ERROR] [localhost] [shared-doc-key-2024022314514s31ww] [user1] nodeJS - error downloadFile:url=http://xxx:9000/document/2025/02/76ebb8899b820ab1d2c62b046589d84a?response-content-type=application%2Fvnd.openxmlformats-officedocument.wordprocessingml.document&response-content-disposition=attachment%3Bfilename%3D%22%E5%AE%9E%E9%AA%8C%E6%8A%A5%E5%91%8A%E6%A8%A1%E6%9D%BF.docx%22&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=Xc77oAly5DsvVberOnoj%2F20250224%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20250224T074943Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=8f288aec732eb469f3ca628ce425bf74b080fe406dc5ee92459fcde9b4797007;attempt=3;code:null;connect:null Error: Error response: statusCode:400; headers:{"accept-ranges":"bytes","content-length":"366","content-type":"application/xml","server":"MinIO","strict-transport-security":"max-age=31536000; includeSubDomains","vary":"Origin","x-amz-id-2":"dd9025bab4ad464b049177c95eb6ebf374d3b3fd1af9251148b658df7ac2e3e8","x-amz-request-id":"182715FD636763C3","x-content-type-options":"nosniff","x-xss-protection":"1; mode=block","date":"Mon, 24 Feb 2025 07:59:19 GMT"};
    at Request.fResponse (/snapshot/server/Common/sources/utils.js)
    at Request.emit (node:events:527:28)
    at Request.onRequestResponse (/snapshot/server/Common/node_modules/request/request.js:1066:10)
    at ClientRequest.emit (node:events:527:28)
    at HTTPParser.parserOnIncomingClient (node:_http_client:631:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:128:17)
    at Socket.socketOnData (node:_http_client:494:22)
    at Socket.emit (node:events:527:28)
    at addChunk (node:internal/streams/readable:315:12)
    at readableAddChunk (node:internal/streams/readable:289:9)
    at Socket.Readable.push (node:internal/streams/readable:228:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

Using curl within a docker container can successfully fetch the file

I've found people with the same problem as me in otherissues, but no one has gotten to the root of the problem:

Actual Behavior

You can open the file normally.

Reproduction Steps

Use any S3 pre-signed url as the file source

Additional information

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions