1import{j as n,H as o}from"./main-B6ad0HGq.js";(function(){try{var e=typeof window<"u"?window:typeof global<"u"?global:typeof globalThis<"u"?globalThis:typeof self<"u"?self:{};e.SENTRY_RELEASE={id:"ea1ea076f7ba40168896c271d7eb9ff92aaf9cd8"};var t=new e.Error().stack;t&&(e._sentryDebugIds=e._sentryDebugIds||{},e._sentryDebugIds[t]="3d365bf0-5fe8-4ed0-8def-9b52cbffd35c",e._sentryDebugIdIdentifier="sentry-dbid-3d365bf0-5fe8-4ed0-8def-9b52cbffd35c")}catch{}})();const s={code:204,name:"No Content",description:"The request succeeded but there is no response body to return. The server processed the request and intentionally sends back an empty body. Common after DELETE operations or form submissions that need no confirmation payload.",causes:["A DELETE request successfully removed a resource. The server confirms deletion but has nothing to return.","A PUT or PATCH request updated a resource and the server chose not to return the updated representation.","A form submission or action endpoint completed successfully but the client does not need any response data."],fixes:["No fix needed â 204 is a valid success response. If your client expects a body, either update the client to handle empty responses or change the server to return 200 with a body.","Do not set a Content-Type or Content-Length header when returning 204 â the response must not contain a body per the HTTP spec.","If your frontend fetch call fails on 204, check that you are not calling response.json() unconditionally. Guard it with a status code check."],monitoringTip:"Uptrack treats 204 as a successful response. If your DELETE or update endpoint suddenly returns a 5xx instead of 204, Uptrack will catch it and alert you."},d=()=>n.jsx(o,{data:s});export{d as component}; 2//# sourceMappingURL=204-C2URsMmv.js.map
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.