CanOfSocks opened a new issue, #12508: URL: https://github.com/apache/trafficserver/issues/12508
I previously made a config in Apache traffic server in 9.2.5 using the apt package available on Debian Bookworm. I have recently made the switch to trying to use the docker container version of traffic server which is on 10.1. I managed to make a configuration in v9.2.5 that worked reliably at being able to resume downloads of large files, and also allowed for multi-threaded downloads with some download manager clients. I tried to use the records convert2yaml.py script to update my records.config to records.yaml and preserve the existing settings as closely as possible to the working v9.2 configuration in 10.1. I also use the slice plugin to create 10MB blocks of large files to help ensure parts of the large files are cached as the connection to the origin is slow and not very stable. For some reason, I cannot get range requests/resumes to work in 10.1. When I run curl directly on the machine, I can receive range requests as expected from the origin server, and the resumable behaviour is restored when I rollback to a snapshot of the innstallation with traffic server v9.2. I have attached a zip of the /etc/trafficserver of both the debian apt v9.2 and docker 10.11 configs for comparison. Alternatively, if someone has a reliable configuration for partial content requests, I would love some more experienced insight of what I can improve. Thanks [trafficserver-v9.2.zip](https://github.com/user-attachments/files/22298018/trafficserver-v9.2.zip) [trafficserver-v10.1.zip](https://github.com/user-attachments/files/22298029/trafficserver-v10.1.zip) -- 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]
