Chrome's caching mechanism caused a weird bug: A winding debugging journey

While debugging a Parquet viewer, the author discovered a crash when accessing S3 storage. After some investigation, the problem was found not to be in the application code, but in Chrome's caching mechanism. When handling range requests, Chrome optimizes caching, but when the server returns a 403 error, Chrome still returns partial data, causing the application to crash. The author reported the issue to the Chromium team, but the team considered it a feature rather than a bug. Eventually, the author chose to fix the issue in OpenDAL. This story reminds us that finding the right trust boundary can significantly speed up debugging.