Ulrich Weber <uweber.li...@gmail.com> wrote:
> From reading the code this fixed the problem when Content-Length
> points to one of the next TCP fragments.
> In our case Content-Length is always 0 with a couple of SUBSCRIBE calls.
> E.g. a TCP packet starting with this will break the SIP connection tracking:
> Content-Length: 0
I guess it makes sense to detect this and then accept for this case too.
> The previous TCP packet was accepted by SIP connection tracking
> because it had no Content-Length field.
Perhaps we should treat Content-length of 0 like "no Conent-Length
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html