Issue Summary

Requests to unpkg.com for Swagger UI assets (e.g., CSS and JavaScript files) are failing due to server-side errors. This issue affects Pode's ability to serve Swagger UI correctly when relying on unpkg.com as the default CDN.

Affected URLs

The following Swagger UI assets hosted on unpkg.com are currently returning errors:

• 🔴 https://unpkg.com/swagger-ui-dist@5/swagger-ui.css
• 🔴 https://unpkg.com/swagger-ui-dist@5/swagger-ui-bundle.js

Steps to Reproduce

1. Open a web browser or use curl to request any of the affected URLs.
2. Observe that unpkg.com fails to serve the requested assets.
3. Check browser dev tools (F12 > Network Tab) or the console for error messages.

Expected Behavior

Swagger UI assets should load correctly from unpkg.com without returning errors.

Actual Behavior

Requests to unpkg.com return HTTP errors (e.g., 504 Not Found ). This prevents Pode from correctly serving Swagger UI when unpkg.com is used as the static asset source.

Workaround

Switching to a different CDN, such as https://cdn.jsdelivr.net/npm

Proposed Resolution

Implement a configurable CDN setting

Additional Information

• Pode users relying on unpkg.com for Swagger UI may experience broken UI or missing assets.
• The issue affects all Pode instances using unpkg.com for static content delivery.