Menu

1 / 2

Why Disabling Downloads Does Not Revoke a Signed URL

DEV Community: backend·Edmond Rätzel·5 days ago
#kKpJUB0q
#devtobackend#devto#dev#request#storage
Reading 0:00
15s threshold

A photographer disables downloads for a private client gallery. The download button disappears immediately. An API test confirms that new download requests return 403 .

Then someone pastes a previously generated file URL into another browser.

The original image still downloads.

Nothing is necessarily broken in the storage service. The application changed its permissions, but an earlier request had already produced a separate credential: a signed URL.

This is a common trap when building private media delivery. The permission check and the actual file transfer happen in different systems, at different times.

A signed URL is a temporary credential

Consider this request flow:

Browser → Application: May I download asset 42?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.