Hello John,
Thanks for your suggestion.
In fact, the request was malformed or it was not recognized.
I'm now using curl to ask for a byte-range, and it worked.
But even after multiple requests for the same asset, ATS will not cache it.
I was expecting that with this plugin in place (cache_range_requests.so), ATS
would cache the whole asset even in the case that Origin does not support
byte.range requests.
In this case, ATS should not rewrite the URL.
So, if ATS could cache the whole asset, it would only need to deliver the
byte-range requested by the client.
I would prefer ATS to not cache every different byte-range request, but cache
the entire response from the Origin, because my Origin is not supporting
byte-range.
This would off-load the origin and make ATS cache more efficient...
Is there a way to configure ATS in that way?
PS: do Comcast have also a mailing list also for Traffic control issues ?
Below is the output of traffic.out logfile.
[Mar 14 17:49:33.013] Server {0x2b8311615700} DIAG: (cache_range_requests)
[cache_range_requests.cc:99] range_header_check(): length: 10,
txn_state->range_value: bytes=0-20
[Mar 14 17:49:33.013] Server {0x2b8311615700} DIAG: (cache_range_requests)
[cache_range_requests.cc:104] range_header_check(): Rewriting cache URL for
http://10.150.139.1/live-spts/media/EPGC7/transmux/192000_160314113551323_2073.ts
to
http://10.150.139.1/live-spts/media/EPGC7/transmux/192000_160314113551323_2073.ts-bytes=0-20
[Mar 14 17:49:33.013] Server {0x2b8311615700} DIAG: (cache_range_requests)
[cache_range_requests.cc:114] range_header_check(): Removed the Range: header
from the request.
[Mar 14 17:49:33.014] Server {0x2b8311615700} DIAG: (cache_range_requests)
[cache_range_requests.cc:121] range_header_check(): Added
TS_HTTP_SEND_REQUEST_HDR_HOOK, TS_HTTP_SEND_RESPONSE_HDR_HOOK, and
TS_HTTP_TXN_CLOSE_HOOK
[Mar 14 17:49:33.019] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:269] set_header(): header: Range, len: 5, val:
bytes=0-20, val_len: 10
[Mar 14 17:49:33.019] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:147] handle_send_origin_request(): Added range header:
bytes=0-20
[Mar 14 17:49:33.020] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:269] set_header(): header: Range, len: 5, val:
bytes=0-20, val_len: 10
[Mar 14 17:49:33.020] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:147] handle_send_origin_request(): Added range header:
bytes=0-20
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:220] handle_server_read_response(): The origin does
not support range requests, attempting to disable cache write.
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:222] handle_server_read_response(): Cache write has
been disabled for this transaction.
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:220] handle_server_read_response(): The origin does
not support range requests, attempting to disable cache write.
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:222] handle_server_read_response(): Cache write has
been disabled for this transaction.
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:168] handle_client_send_response(): result: 0
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:177] handle_client_send_response(): 200 OK
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:269] set_header(): header: Range, len: 5, val:
bytes=0-20, val_len: 10
[Mar 14 17:49:33.122] Server {0x2b8309f35500} DIAG: (cache_range_requests)
[cache_range_requests.cc:188] handle_client_send_response(): added range
header: bytes=0-20
Thanks for your help.
Nuno
Nuno Baeta
nuno.ba...@nos.pt
Direção de Plataformas Core e Serviços
F: +351 210 1045 32 M:+351 931 019 532
Av. D. João II, Lote 1.06.2.4, Piso 4 , 1998-030 Lisboa - Portugal
-----Original Message-----
From: Rushford, John [mailto:john_rushf...@cable.comcast.com]
Sent: 11 de março de 2016 19:29
To: dev@trafficserver.apache.org
Subject: Re: ATS byte-range requests
Nuno,
You can enable debugging in records.config:
CONFIG proxy.config.diags.debug.enabled INT 1 CONFIG
proxy.config.diags.debug.tags STRING cache_range_requests
Re-run your testing to see if the Range Request header is recognized.
Thanks
--
John J. Rushford
IPCDN Engineering
1400 Wewatta Street, Denver Colorado 80202 john_rushf...@cable.comcast.com
From: Nuno Jose Baeta <nuno.ba...@nos.pt<mailto:nuno.ba...@nos.pt>>
Reply-To: "dev@trafficserver.apache.org<mailto:dev@trafficserver.apache.org>"
<dev@trafficserver.apache.org<mailto:dev@trafficserver.apache.org>>
Date: Friday, March 11, 2016 at 12:17 PM
To: "dev@trafficserver.apache.org<mailto:dev@trafficserver.apache.org>"
<dev@trafficserver.apache.org<mailto:dev@trafficserver.apache.org>>
Cc: Pedro Miguel Marques <pedro.m.marq...@nos.pt<mailto:pedro.m.marq...@nos.pt>>
Subject: RE: ATS byte-range requests
Hello,
I'm trying to get ATS work with byte-range requests.
I have installed version 5.3.2, configured as a HTTP cache proxy.
On my remap.config file, I inserted the following:
@plugin=cache_range_requests.so
The server is responding with the whole content, with HTTP 200 status.
What I'm doing wrong?
Thanks
Nuno
[roda]
Nuno Baeta
Direção de Plataformas Core e Serviços
Plataformas
F: +351 210 1045 32 M:+351 931 019 532
nuno.ba...@nos.pt<mailto:nuno.ba...@nos.pt>
Av. D. João II, Lote 1.06.2.4, Piso 4
1998-030 Lisboa - Portugal
[logo_simples]
AVISO
A informação contida neste e-mail e ficheiros anexos são confidenciais e
deverão ser lidos exclusivamente pela pessoa ou entidade a quem se dirigem. Se
recebeu esta comunicação por engano, por favor, informe de imediato o remetente
e apague a mensagem e os ficheiros anexos sem os ler, copiar, gravar,
distribuir ou divulgar ou fazer qualquer outro uso da informação. Lembre-se da
sua Responsabilidade Social Ambiental antes de decidir imprimir este e-mail.
DISCLAIMER
The information in this email is confidential and should only be read by the
person or entity to whom it is addressed. If you have received this
communication by mistake, please notify the sender and immediately delete the
message and the attached files without reading, copying, recording,
distributing, disseminating or making any other use of the information.
Remember your Environmental Responsibility before deciding to print this email.
