BharathPESU commented on issue #12508: URL: https://github.com/apache/trafficserver/issues/12508#issuecomment-3487440724
Hi — I’d like to take this issue and help diagnose/fix the regressions in partial content / range requests between Traffic Server v9.2.5 (Debian apt) and v10.1 (Docker). What I’ve observed so far: Range/resume requests work when using the v9.2.5 setup, but stop working after moving to the v10.1 Docker image. curl against the origin still returns valid range responses. Rolling back to v9.2 restores resumable behaviour. I used convert2yaml.py to translate records.config → records.yaml and I’m also using the slice plugin (10MB blocks) in both setups. I’ve attached a zip with /etc/trafficserver from both environments for comparison. Plan / first steps I will take: Compare effective records.yaml / records.config differences and evaluate any new or changed default settings in 10.x that could affect range handling or cache partial responses. Verify plugin and header handling differences (slice plugin, Cache-Control, Range, Accept-Ranges, conditional responses). Reproduce the issue with minimal config and a reproducible origin that serves 206 Partial Content for range requests, to isolate whether the problem is in ATS request parsing, cache lookup/serve logic, or plugin interaction. Test scenarios with http/1.1 vs http/2 to see if protocol differences between v9 and v10 affect behavior. Propose a config change or code fix and open a PR or provide step-by-step config guidance depending on findings. Could you please assign this issue to me? I’m happy to open a PR or post incremental findings here as I go. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
