https://bz.apache.org/bugzilla/show_bug.cgi?id=60599
--- Comment #2 from Jeff Wheelhouse <[email protected]> --- Upon investigation, I found that when mod_cache is returning a revalidated response with a 304 status code, as is the case here, all it sends along the filter stack is a single EOS bucket, with the relevant headers already set in r->headers_out. mod_http2 appears to check for a body bucket before creating a h2_headers bucket. Since there's not one in this case, the mod_http2 code treats this case as if there is no response at all. The provided patch assumes that if there is no body and the status code is 304, then it is OK to go ahead with no body and just prepend the h2_headers bucket to the brigade. This seems to work, but I suspect there may be various other cases where it's OK that there's no body that are not handled by this patch. A more generic approach to determining that would possibly be more suitable. r->header_only sounds like it would be super helpful here but, alas, that seems not to be the case. Thanks! -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
