[
https://issues.apache.org/jira/browse/TS-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787635#comment-13787635
]
ASF subversion and git services commented on TS-2212:
-----------------------------------------------------
Commit 8d17457f1fe5f91a10bb790d89019f88145b6479 in branch refs/heads/master
from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=8d17457 ]
TS-2212 Implement <fsiz> tag for HTTP
The current docs explains it as
``fsiz``
The size of the file (*n* bytes) as seen by the origin server.
However, there's nothing that implements this. This code will
try its best to find a body size, based on origin response
headers such as Content-Range and bytes read.
It's somewhat unfortunate that at the time of logging, the CacheVC
is no longer evailable, and all headers are already modified such
that they reflect client's e.g. Range: bytes= header.
This patch implements the logic around using the Range-response
headers when available, and the internal (full) byte counters
when not.
Finally, this also generalizes the "atoi" functionality in lib/ts
(ParseRules) such that the prototypes with and without a string
length are available for all int types. This was needed in order
to do an efficient and safe atoi on the not-null terminated string
to a 64-bit int.
> The <fsiz> log-tag is not implemented (for HTTP or anything)
> ------------------------------------------------------------
>
> Key: TS-2212
> URL: https://issues.apache.org/jira/browse/TS-2212
> Project: Traffic Server
> Issue Type: New Feature
> Components: Logging
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 4.1.0
>
>
> This should be the object size as returned from origin, or cache, and should
> always be the same regardless of what the client requests (e.g. if client
> asks for a Range: the fsiz should be the total object size).
> This tag is documented in the docs, but it's not implemented at all.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
