Error 5408 設計檢視:為何要在提交前檢查限制
Error 5408 is a design review: check the limit before you send it
Agent 系統應在執行前核驗權限範圍、期限及撤銷狀態,避免操作完成後才取消結果。Cloudflare Images 直接上載的檔案超過約 10MB 會因錯誤 5408 而逾時;建議在瀏覽器壓縮,並在用戶端驗證檔案大小、格式及尺寸。United 自 11 月 11 日起禁止未獲授權的 AI agent 預訂、更改或處理機票,文章認為權限應在操作前核驗。
United's agent ban, one more time, but from the builder's chair.
Since November 11, an unauthorized AI agent cannot book, change or service a United ticket, even with the passenger supervising. United can cancel an agent-made booking without notice. The enforcement shape is the interesting part for anyone shipping agents: the check happens after the work is done. Booking made, confirmation sent, then gone.
That is the worst failure mode in any system, and you already know why from your own stack. A failure discovered after success is worse than a clean refusal up front, because everything downstream has already committed to the result.
Today's corpus evidence is mundane and that is the point. Cloudflare Images direct creator uploads time out with error 5408 once a file passes roughly 10MB. The documented fix is not retry harder. It is: compress in the browser before upload, keep direct uploads under about 10MB, and validate size, format and dimensions client-side so an oversize file gets rejected with a clear message instead of a timeout nobody can act on. One more detail worth stealing: if the upload returns 200 but the image never shows in the dashboard, check for draft:true and confirm completion with a GET on the image ID. A 200 is not proof the thing landed.
Full skill, with the source thread: https://vectle.com/skills/skl_AgY6X9vSd74k-OMOKOq7dg
Map that onto delegation and the United argument mostly dissolves. The passenger side is right that consent was given: money, miles, explicit instruction. The United side is right that a borrowed password cannot express scope and cannot distinguish user, agent and fraud bot. Both of those are arguments for checking a scoped permission before the action, not for canceling the result after it. Preflight validation is a solved pattern everywhere else in the stack. Delegation is just late to it.
If you ship agents: validate the permission like you validate the payload. Scope, expiry and revocation checked before the call, a refusal that names the reason, and a human step reserved for the parts that are legally personal. Do not build the version that succeeds silently and gets unwound later.
We publish skills like the Cloudflare one, distilled from real agent debugging threads, at https://vectle.com, and we argued the passenger versus airline sides on this week's Skill Report: https://open.spotify.com/episode/3fYLN1Q1kcenw0EDrhWJwz
Question for the comments: if you told your agent to book it, with your money and your miles, should an airline be able to cancel the booking just because an agent made it, or should a ban hold until agents carry a scoped, revocable permission the airline can verify up front?
來源:DEV Community · dev.to