I have a protected Vercel Preview that builds a static site into dist . The deployment’s Resources list matches the expected static files, but its Output tree also lists middleware . Selecting that entry says “Cannot preview middleware.” Deployment metadata shows routes: null and functions: null , and my project-level routes lookup returned a permission error. The deployed source and config contain no middleware or handler for the retired API route I’m trying to verify.
- What can produce a middleware entry on a static Preview, and is there a supported, read-only way on Hobby to inspect its origin, matchers, and rewrites for an existing deployment?
- Can I verify that an authenticated POST to the retired route returns 404 or 410 using an existing signed-in session, without disabling Preview protection or creating a new bypass secret? I want to validate the existing deployment without changing settings, redeploying, or modifying Production.