Need to know a way to handle error message more accurately

Hi there

Similar to other S3 compatible storages, DigitalOcean Spaces doesn’t allow customizing the default “Access Denied” error page for signed URLs directly.

To create a user-friendly experience, you can implement a front-end error handling to catch 403 responses and display a custom message or redirect users to a custom error page based on your exact application needs.

- Bobby

Heya, @deepakjha

You can handle errors by checking the validity of the signed URL before making the request from the client. Instead of directly using the signed URL in the front-end.

On the server-side, check whether the signed URL is valid and accessible before redirecting the user to it. This can help ensure that expired or invalid URLs don’t reach the user.

Also you can create a backend route that acts as a proxy between the user and DigitalOcean Spaces. This way, if a signed URL is invalid or expired, you can send a custom error message or redirect users to an alternative solution without exposing raw access errors.

Regards