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

Is possible use same url after upgrade? #106

Closed
taaum opened this issue Jun 19, 2019 · 8 comments
Closed

Is possible use same url after upgrade? #106

taaum opened this issue Jun 19, 2019 · 8 comments

Comments

@fabiovasini
Copy link

You can still use Thumbor even with the new version.

@taaum
Copy link
Author

taaum commented Jun 20, 2019

when i try old URL i did see error message
{
"status": 500,
"code": "NoSuchKey",
"message": "The specified key does not exist."
}

how fix it?

@hayesry
Copy link
Member

hayesry commented Jun 20, 2019

@taaum Are you trying to use the Thumbor request style for images located within subfolders of your S3 bucket? If so, that will probably throw the NoSuchKey error.

@calvinmuller
Copy link

so how do you access images in a subfolder in a bucket?

@hayesry
Copy link
Member

hayesry commented Jun 20, 2019

@calvinmuller Accessing images in subfolders isn't currently available via the Thumbor mappings; however, it's fully supported using the encoded request format. We've added this to our backlog though as we continue to iterate on those mappings based on your feedback!

@taaum
Copy link
Author

taaum commented Jun 24, 2019

thank you @hayesry for your response.
I found to solve this issue, use Cloudflare worker convert Thumbor style to Sharp base64 style.

@ahmetcetin39
Copy link

Cloudflare

Hi @taaum Can you explain how to do this please?
I used to have the urls in this format before -> abcdefgh.cloudfront.net/member/asdsad.png
I am able to use them unless I move them to the root directory.

@beomseoklee
Copy link
Member

We have updated our solution, and I believe your issue has been fixed. If you still see the issue with the latest version (v4.2), please feel free to reopen the issue.

You can refer to the recent changes here

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

7 participants