Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong image returned for proxified url #47

Open
noumantahir opened this issue Nov 7, 2024 · 0 comments
Open

Wrong image returned for proxified url #47

noumantahir opened this issue Nov 7, 2024 · 0 comments

Comments

@noumantahir
Copy link
Collaborator

noumantahir commented Nov 7, 2024

Problem Statement

url for image posted by user get ignored and a wrong image is display in it's place.
Screenshot 2024-11-07 at 19 35 28

Post Link
https://ecency.com/hive-193084/@jza/q083jdy00ba2uc6e968z10#@jza/re-jza-2024117t5013704z

Assessment

I have an assessment for this issue, however I can only go this far since rest is handled by backend...

the b58 string generated for regular url present in post body equals to the following

https://images.d.buzz/1000011014.jpg.jpeg

TO

Pufd3b1W2k6xMGE5XYWsBQPD2tfjErFbURHRR2EkYv5Td3k5929uAWLW

The final proxified url is below..

https://images.ecency.com/p/Pufd3b1W2k6xMGE5XYWsBQPD2tfjErFbURHRR2EkYv5Td3k5929uAWLW.webp

but this url points to a wrong image that is not represented by the actual real url.

so what I believe is happening, there is some other image in backend whose hash matches with b58 string and the actual image gets ignored since it is apparent there must be a priority set in back to prioritise the other image.

This one is not the case of image not found, like the issue we dealt with some days back, this wrong image actually exist in backend

Screenshot 2024-11-07 at 19 35 06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant