[squid-users] filter NONE/000 NONE error:transaction-end-before-headers

[amaury at tin.it]

Hello
I would like to filter the message NONE/000 NONE error:
transaction-end-before-headers - HIER_NONE/- - - HTTP/0.0 "-" 0 0 that 
it arrives from
loadbalancer keep alived. I have red that It was/is a 
bug.
I'm using squid-4.12 and reading documentation there are this two 
point, that I could be useful:

#       acl aclname note [-m
[=delimiters]] name [value ...]
#         # match transaction 
annotation [fast]
#         # Without values, matches any annotation 
with a given name.
#         # With value(s), matches any annotation 
with a given name that
#         # also has one of the given values.

#         # If the -m flag is used, then the value of the named

#         # annotation is interpreted as a list of tokens, and the ACL

#         # matches individual name=token pairs rather than whole

#         # name=value pairs. See "ACL Options" above for more info.

#         # Annotation sources include note and adaptation_meta 
directives
#         # as well as helper and eCAP responses.


#       
acl aclname has component
#         # matches a transaction "component" 
[fast]
#         #
#         # Supported transaction components are:

#         #  request: transaction has a request header (at least)

#         #  response: transaction has a response header (at least)

#         #  ALE: transaction has an internally-generated Access Log 
Entry
#         #       structure; bugs notwithstanding, all 
transaction have it 
#         #
#         # For example, the following 
configuration helps when dealing with HTTP
#         # clients that 
close connections without sending a request header:
#         #

#         #  acl hasRequest has request
#         #  acl logMe note 
important_transaction
#         #  # avoid "logMe ACL is used in 
context without an HTTP request" warnings
#         #  access_log ... 
logformat=detailed hasRequest logMe
#         #  # log request-less 
transactions, instead of ignoring them
#         #  access_log ... 
logformat=brief !hasRequest
#         #
#         # Multiple components 
are not supported for one "acl" rule, but
#         # can be specified 
(and are ORed) using multiple same-name rules:
#         #
#         #  
# OK, this strange logging daemon needs request or response,
#         
#  # but can work without either a request or a response:
#         #  
acl hasWhatMyLoggingDaemonNeeds has request
#         #  acl 
hasWhatMyLoggingDaemonNeeds has response

Please could you give me a 
practical example example that how it works the:
#       acl aclname 
note [-m[=delimiters]] name [value ...] ?

Thank you
Best regards