[backport rh-test] [bugfix] add mode: no-cors to fix CORS error when following GCS redirects (#6278)

Backport of #6277 to `rh-test`

Automatically created by backport workflow.

Co-authored-by: Christian Byrne <cbyrne@comfy.org>
This commit is contained in:
Comfy Org PR Bot
2025-10-25 15:12:18 +09:00
committed by GitHub
parent 71e851acfa
commit 3954ac8584

View File

@@ -70,16 +70,17 @@ self.addEventListener('fetch', (event) => {
// Handle redirects to external storage (e.g., GCS signed URLs) // Handle redirects to external storage (e.g., GCS signed URLs)
if (response.type === 'opaqueredirect') { if (response.type === 'opaqueredirect') {
// Opaqueredirect: redirect occurred but response is opaque (headers not accessible) // Opaqueredirect: redirect occurred but response is opaque (headers not accessible)
// Re-fetch the original /api/view URL with redirect: 'follow' // Re-fetch the original /api/view URL with redirect: 'follow' and mode: 'no-cors'
// Browser will: // - mode: 'no-cors' allows cross-origin fetches without CORS headers (GCS doesn't have CORS)
// 1. Send auth headers to /api/view (same-origin) // - Returns opaque response, which works fine for images/videos/audio
// 2. Receive 302 redirect to GCS // - Browser will send auth headers to /api/view (same-origin)
// 3. Automatically strip auth headers when following cross-origin redirect // - Browser will receive 302 redirect to GCS
// 4. Use GCS signed URL authentication instead // - Browser will follow redirect using GCS signed URL authentication
return fetch(event.request.url, { return fetch(event.request.url, {
method: 'GET', method: 'GET',
headers: headers, headers: headers,
redirect: 'follow' redirect: 'follow',
mode: 'no-cors'
}) })
} }