iOS Safari下Google Cloud Storage Bucket的CORS配置无法获取TXT文件

I’ve run into similar edge cases with CORS on Google Cloud Storage (GCS) and iOS Safari before—let’s break down why your .txt files might be failing while .jpg files work, and walk through actionable fixes.

Possible Causes & Step-by-Step Fixes #

1. MIME Type Misconfiguration #

iOS Safari is notoriously strict about MIME types for text resources, and this is a common culprit when media files work but text doesn’t:

• First, verify that your .txt files in GCS have the correct text/plain MIME type. Sometimes GCS auto-detects this incorrectly during upload. You can fix this via the GCS console, or use the gsutil command to batch-update files:

  gsutil setmeta -h "Content-Type:text/plain" gs://your-bucket/**/*.txt
  

• Update your CORS config to explicitly include Content-Type in both allowedHeaders and exposeHeaders (if your frontend needs to read response headers).

2. Preflight Request Handling Quirks #

iOS Safari treats text files differently when processing preflight OPTIONS requests compared to media files like images:

• Ensure your CORS config explicitly allows the OPTIONS method (it’s easy to overlook this even if GET is allowed). Here’s a robust example config to use:

  [
    {
      "origin": ["https://your-web-domain.com"],
      "method": ["GET", "OPTIONS"],
      "responseHeader": ["Content-Type", "Authorization"],
      "maxAgeSeconds": 3600
    }
  ]
  

  Apply this config with:

  gsutil cors set cors-config.json gs://your-bucket
  

• Avoid using a wildcard * for allowedOrigins if possible—iOS Safari can be stricter with wildcard origins for non-media resources.

3. Caching or Browser-Specific Restrictions #

iOS Safari often caches CORS responses aggressively, which can lead to outdated rules being applied:

• Clear Safari’s cache and website data on your iOS device (go to Settings > Safari > Clear History and Website Data)
• Test your request in a private browsing window to rule out cached responses
• Double-check your JavaScript fetch request: avoid adding custom headers unless they’re explicitly allowed in your CORS config—iOS Safari may block text requests with unapproved headers.

4. Hidden Permission Issues #

Even with correct CORS settings, restrictive bucket/object permissions can cause silent failures in iOS Safari (unlike images, which sometimes have more lenient handling):

• Confirm your bucket’s IAM permissions or object-level ACLs allow public access (or access from your web origin) for .txt files. If using signed URLs, ensure they’re generated with valid GET permissions and haven’t expired.

Pro Tip for Debugging #

Connect your iOS device to a Mac and use Safari’s developer tools to inspect the network request. Check the console for specific errors (like preflight failures or MIME type mismatches)—this will cut down troubleshooting time significantly.

内容的提问来源于stack exchange，提问作者Stefano