You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "jaekyung oh (JIRA)" <ji...@apache.org> on 2013/10/01 11:36:32 UTC
[jira] [Created] (TS-2262) range request for cached content with
small size(around 2k bytes) fails.
jaekyung oh created TS-2262:
-------------------------------
Summary: range request for cached content with small size(around 2k bytes) fails.
Key: TS-2262
URL: https://issues.apache.org/jira/browse/TS-2262
Project: Traffic Server
Issue Type: Bug
Reporter: jaekyung oh
after cache a content with 2k bytes size, range request for it fails showing timeout.
Version : ATS 3.2.4
curl -v -o /dev/null --range 100-200 "http://ats-test.test.net/1-test.2k" shows
* About to connect() to ats-test.test.net port 80 (#0)
* Trying 110.45.197.30... % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0connected
* Connected to ats-test.test.net (xxx.xxx.xxx.xxx) port 80 (#0)
> GET ats-test.test.net/1-test.2k HTTP/1.1
> Range: bytes=100-200
> User-Agent: curl/7.20.1 (x86_64-unknown-linux-gnu) libcurl/7.20.1 OpenSSL/1.0.0 zlib/1.2.5 libidn/1.15 libssh2/1.2.2_DEV
> Host: ats-test.test.net
> Accept: */*
>
< HTTP/1.1 206 Partial Content
< Accept-Ranges: bytes
< ETag: "2429143783"
< Last-Modified: Mon, 22 Apr 2013 07:46:30 GMT
< Date: Tue, 01 Oct 2013 09:15:00 GMT
< Server: ATS/3.2.4.3.0
< Content-Type: multipart/byteranges; boundary=RANGE_SEPARATOR
< Content-Length: 1000
< Age: 172
< Connection: keep-alive
<
{ [data not shown]
0 1000 0 1 0 0 0 0 --:--:-- 0:00:30 --:--:-- 0* transfer closed with 999 bytes remaining to read
0 1000 0 1 0 0 0 0 --:--:-- 0:00:30 --:--:-- 0* Closing connection #0
curl: (18) transfer closed with 999 bytes remaining to read
is there any limit on the size of contents for range request processing?
--
This message was sent by Atlassian JIRA
(v6.1#6144)