Boto3 presigned url causes browser rendering issues

[didemkkaslan]

Describe the bug

Our backend uses boto3 to generate presigned urls and in our dashboard app we are showing user avatars ( uploaded to s3 from dashboard again) using those s3 presigned urls. The issue is some of those presigned urls are buggy that they cause rendering issues for chrome. We are using antd table to showcase use avatars and two rows highlighted at the same time because of some of the presigned urls.

Expected Behavior

All of the presigned urls should works and not cause any rendering issues.

Current Behavior

Antd table multiple rows highlighted at the same time.

https://github.com/boto/boto3/assets/106841409/ba6e46ac-cc2c-4f5a-b6da-d3998f5fd944

Reproduction Steps

Just use antd table together with img tag with src includes buggy presigned url such as

example buggy presigned url: https://prod-cdkcoreplatformstac-platformresourcesbucketf-1n0ugzne0lks9.s3.amazonaws.com/user_avatars_8c046bd8-9ad8-4ea3-b70d-74723b5e54eb?response-content-type=image%2Fpng&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIARPTIMKGIESFD22FX%2F20240207%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20240207T102220Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=dade451b455468f127a547b7eb9b5c400f847f7b07a381eea36e2e1456ae46ba

or just try this reproduction template:

Possible Solution

No response

Additional Information/Context

No response

SDK version used

2.96.2

Environment details (OS name and version, etc.)

Mac, Chrome

[tim-finnigan]

Hi @didemkkaslan thanks for your patience here. I'm getting a "Sandbox not found" when clicking the reproduction link. Can you share the steps to reproduce here or provide any updates?

Also the latest Boto3 version is 1.34.100 per the CHANGELOG, so I'm not sure if the 2.96.2 you referenced is the version of your frontend framework or something else.

[github-actions[bot]]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.