[
https://issues.apache.org/jira/browse/TS-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951191#comment-13951191
]
ASF GitHub Bot commented on TS-2553:
------------------------------------
Github user jablko commented on the pull request:
https://github.com/apache/trafficserver/pull/63#issuecomment-38952957
The metalink/test/pipeliningDisconnect script in commit 45393e reproduces
the crash two out of three times on my system, but if it's a race condition it
might manifest with different frequency on different systems? Unfortunately I
haven't figured out yet how to exercise it deterministically from "outside"
Traffic Server (by using just a combination of requests/responses and config
settings). Any advice on how to expose it more predictably?
> Fix a segfault in the Metalink plugin reported by Faysal Banna and preserve
> the Content-Length header
> -----------------------------------------------------------------------------------------------------
>
> Key: TS-2553
> URL: https://issues.apache.org/jira/browse/TS-2553
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
> Reporter: Jack Bates
> Assignee: James Peach
> Fix For: 5.0.0
>
>
> Fix a segfault in the Metalink plugin reported by Faysal Banna:
> https://github.com/jablko/dedup/issues/1
> Copy the upstream nbytes (if known) downstream to preserve the Content-Length
> header.
> Improve comments in the plugin code.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
