Windsurf storage

Signed URLs Expiring Too Fast in Windsurf App

Images, documents, and file download links in your Windsurf-generated app break after a short time. Users see broken images, get access denied errors when clicking download links, or see files that loaded fine moments ago now showing 403 Forbidden errors.

This happens because your app uses signed URLs to serve files from private cloud storage (Supabase Storage, S3, or GCS), and the URLs expire too quickly. Cascade may have set a very short expiration time, or the URLs are being generated once and cached while the expiration passes.

The issue is especially frustrating for users because everything appears to work initially, then breaks silently. Pages that worked fine a few minutes ago suddenly show broken images everywhere.

Error Messages You Might See

403 Forbidden: Request has expired AccessDenied: Request has expired The provided token has expired SignatureDoesNotMatch Error: URL signature expired
403 Forbidden: Request has expiredAccessDenied: Request has expiredThe provided token has expiredSignatureDoesNotMatchError: URL signature expired

Common Causes

  • Default short expiration — Cascade used the default signed URL expiration (often 60 seconds) without increasing it for the use case
  • URLs cached but not refreshed — Signed URLs are generated once at page load and stored in state, but not regenerated when they expire
  • Server-side rendering with stale URLs — URLs generated during SSR are already partially expired by the time the client receives them
  • Email or notification links — Signed URLs sent in emails expire before the recipient opens the message
  • CDN caching conflicts — A CDN caches the page with signed URLs, but the URLs expire before the CDN cache does

How to Fix It

  1. Increase signed URL expiration — Set expiration to match your use case: 1 hour for page views, 24 hours for download links, 7 days for email links
  2. Implement URL refresh logic — Create a client-side mechanism that regenerates signed URLs before they expire, or on 403 errors
  3. Use public buckets for non-sensitive files — If the files aren't private (like product images), make the bucket public and skip signed URLs entirely
  4. Add a redirect endpoint — For email links, create a permanent URL (/files/:id/download) that generates a fresh signed URL and redirects
  5. Set CDN cache to match URL expiration — Ensure CDN cache-control headers expire before the signed URLs they contain

Real developers can help you.

Simon A. Simon A. I'm a backend developer building APIs, emulators, and interactive game systems. Professionally, I've developed Java/Spring reporting solutions, managed relational and NoSQL databases, and implemented CI/CD workflows. Victor Denisov Victor Denisov Developer Matthew Jordan Matthew Jordan I've been working at a large software company named Kainos for 2 years, and mainly specialise in Platform Engineering. I regularly enjoy working on software products outside of work, and I'm a huge fan of game development using Unity. I personally enjoy Python & C# in my spare time, but I also specialise in multiple different platform-related technologies from my day job. Alvin Voo Alvin Voo I’ve watched the tech landscape evolve over the last decade—from the structured days of Java Server Pages to the current "wild west" of Agentic-driven development. While AI can "vibe" a frontend into existence, I specialize in the architecture that keeps it from collapsing. My expertise lies in the critical backend infrastructure: the parts that must be fast, secure, and scalable. I thrive on high-pressure environments, such as when I had only three weeks to architect and launch an Ethereum redemption system with minimal prior crypto knowledge, turning it into a major revenue stream. What I bring to your project: Forensic Debugging: I don't just "patch" bugs; I use tools like Datadog and Explain Analyzers to map out bottlenecks and resolve root causes—like significantly reducing memory usage by optimizing complex DB joins. Full-Stack Context: Deep experience in Node.js and React, ensuring backends play perfectly with mobile and web teams. Sanity in the Age of AI: I bridge the gap between "best practices" and modern speed, ensuring your project isn't just built fast, but built to last. zipking zipking I am a technologist and product builder dedicated to creating high-impact solutions at the intersection of AI and specialized markets. Currently, I am focused on PropScan (EstateGuard), an AI-driven SaaS platform tailored for the Japanese real estate industry, and exploring the potential of Archify. As an INFJ-T, I approach development with a "systems-thinking" mindset—balancing technical precision with a deep understanding of user needs. I particularly enjoy the challenge of architecting Vertical AI SaaS and optimizing Small Language Models (SLMs) to solve specific, real-world business problems. Whether I'm in a CTO-level leadership role or hands-on with the code, I thrive on building tools that turn complex data into actionable value. PawelPloszaj PawelPloszaj I'm fronted developer with 10+ years of experience with big projects. I have small backend background too Vlad Temian Vlad Temian 15+ years shipping production infrastructure for startups. Former CTO at qed.builders (acquired by The Sandbox). Cursor ambassador and agentic tooling builder. I've scaled systems, automated deployments, and built observability tools for AI coding workflows. I specialize in taking vibe-coded apps from broken prototype to production-ready: fixing Supabase auth/RLS, Stripe integrations, deployment pipelines, and cleaning up AI-generated spaghetti. I build tools in this space (agentprobe, claudebin, micode) and understand both sides: how AI generates code and why it breaks. https://blog.vtemian.com/ Antriksh Narang Antriksh Narang 5 years+ Experienced Dev (Specially in Web Development), can help in python, javascript, react, next.js and full stack web dev technologies. Krishna Sai Kuncha Krishna Sai Kuncha Experienced Professional Full stack Developer with 8+ years of experience across react, python, js, ts, golang and react-native. Developed inhouse websearch tooling for AI before websearch was solved : ) ISHANTDEEP SINGH ISHANTDEEP SINGH Senior Software Engineer with 7+ years of experience in React, JavaScript, TypeScript, Next.js, and Node.js. I’ve also worked as a tech lead for startups, owning end-to-end technical execution including architecture, development, scaling, and delivery. I bring a strong mix of hands-on coding, product thinking, and technical leadership, and I’m comfortable building products from scratch as well as improving and scaling existing systems.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help

Frequently Asked Questions

How long should I set signed URL expiration?

It depends on the use case. For images displayed on pages: 1-4 hours. For download links: 24 hours. For links in emails: 7 days. For public content that doesn't need access control, skip signed URLs and use public buckets.

Can signed URLs be extended after they are created?

No. Once a signed URL is generated, its expiration is fixed. You must generate a new signed URL. Design your app to either refresh URLs before expiry or use a redirect endpoint that generates fresh URLs on demand.

Related Windsurf Issues

Can't fix it yourself?
Real developers can help.

You don't need to be technical. Just describe what's wrong and a verified developer will handle the rest.

Get Help