jerebear12

@betwowt @chrislusf I am still seeing the error. To test new changes, I followed these [instructions](https://github.com/seaweedfs/seaweedfs#installation-guide) and tried using the same program I had used to upload the files. The...

@betwowt Yes, I deleted the instance of seaweed off of my WSL machine, and all seaweed processes were stopped. I then reinstalled seaweed. I downloaded the S3 browser tool, and...

@imfantuan I could not reproduce the error you're describing. I see completely different XML being POSTed to the S3 gateway in my requests: ~~~~xml 1"d41d8cd98f00b204e9800998ecf8427e-0"video.mp4http://example.com:8888/buckets/1/video.mp4 ~~~~ The response is 200,...

@imfantuan I found what you found. In the request payload, I'm sending this to the S3 gateway: ~~~~xml ~~~~ However, in my browser, I don't get a response of 400...

Have you tried `npm install esbuild` or `npm install -g esbuild` If that doesn't work can you try `npm install` again? I am not familiar with this error so I'm...

> no time to learn this. please create a docker image to reproduce. We are not able to create an image for reproduction because of issues with the S3 SDK...

@imfantuan This is good information but not a fix for us. As you can tell by the code I provided we are using the high-level implementation of the S3 SDK....

I believe POST requests made by the browser will always have an Origin header that contains the request's address. I think PUT and DELETE will as well.

@chrislusf We are still getting this error. Any suggestions?

Thanks. I'm testing a few things with that code.