[DEV_LOG] PHASE 1.7.5.b: CORE_LOGIC_ERROR
Mid-week update: It’s worse than it looks. A cascade of ReferenceErrors and TypeErrors is hitting the original build.
Diagnosis: Identified a failed "Lazy Import" implementation. The browser is triggering a terminal CORS failure on load. Manifest loading is blocked. PWA/Offline capabilities are dark.
We are sitting with the wreckage for now.
LaravelのBladeとCORS設定をAWS（S3 / API Gateway）で再現してみよう
https://qiita.com/chaochire/items/9be1c47cad3913ff516e?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items
Just lost several hours of my life to silly CORS issues while setting up https://static-s.umeyashiki.org as my Akkoma media base URL 
Nginx “gotcha”: header inheritance.
If you put an add_header directive inside a location block, it completely suppresses all add_header directives defined in the parent server block.
Patrick 
datatofu
Qiita - 人気の記事
Yukaserver {
add_header "X-Hdr-A" "Value";
add_header "X-Hdr-B" "Value";
location / {
add_header "X-Hdr-C" "Value"; # <-- This wipes out A and B!
access_log /var/log/a.log;
}
location /bb {
access_log /var/log/b.log; # <-- A and B will show up here just fine.
}
}
If your global headers are mysteriously disappearing on certain paths, maybe check your location blocks.
I'm working on setting up my own #PeerTube and #loops instances in #quebec #canada I've never used S3 storage, so I need to learn how that works. In …
Ooooh, fcuk, it is even worse. I do a JavaScript fetch request. Internally it notices that it needs to do its CORS OPTIONS magic first. That one fails with a 404, as the developer tools show. But the fetch request itself fails. No, it does not come back with a 404 response. It just fails the fetch with
TypeError: Failed to fetch
This even though the OPTIONS response says
Access-Control-Allow-Origin *
beside the 404. This is baaaad!
Fun with #CORS.
Many web devs come across CORS eventually, first reaction being WTF. Then see Stackoverflow or a chatty text randomizer to find.
The server response lacks the Access-Control-Allow-Origin header
which is confusing, as you're dealing with two servers at this point.
I thought to understand it, but debugged an hour to find that an OPTIONS request for .../blabla does not follow the redirect to .../blabla/ (in Firefox at least) .😠
For schedules that block cross-origin access in the browser (e.g. #FOSDEM), there's now a small companion project: the Skedz CORS Proxy. A simple proxy with a domain whitelist, easy to self-host or run locally.
Public instance: https://cors.skedz.org
Example: https://cors.skedz.org/https://fosdem.org/2026/schedule/xml
Source (AGPLv3): https://github.com/ysorge/skedz-cors-proxy
Frank
Harald
Afroféminas
Kitsune / Yves 👾