[
https://issues.apache.org/jira/browse/TS-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660244#comment-14660244
]
Leif Hedstrom commented on TS-3826:
-----------------------------------
Do you have negative caching enabled in records.config? From what it looks
like, you hit upon this code:
{code}
if (t_state.negative_caching && t_state.hdr_info.server_response.status_get()
== HTTP_STATUS_NO_CONTENT) {
int s = sizeof("No Content") - 1;
buf->write("No Content", s);
nbytes += s;
}
{code}
There are two places where we do this (different paths). If you can, just try
to remove this, and see what happens?
I bet, but not 100% sure, that this is an artifact that ATS did not allow
caching empty documents in the past. There's now a setting for this:
{code}
CONFIG proxy.config.http.cache.allow_empty_doc INT 1
{code}
So, maybe, just maybe, we should eliminate this "dummy" body ? If to, that
might be a 6.0.0 fix that we should consider right now, since this would be the
time to break compatibility.
> Traffic Server add message "No Content" to response when is 204 code.
> ---------------------------------------------------------------------
>
> Key: TS-3826
> URL: https://issues.apache.org/jira/browse/TS-3826
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 4.2.0
> Reporter: fengidri
> Labels: newbie
> Fix For: 6.0.0
>
>
> I found that When the 204 response is cached, the response from the
> cache will be added "No Content" message.
> Why? Anybody know this?
> Thanks!!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
