> The proxy.process.https stats (only 2 stats) should also be considered
when overhauling the stats. They are really TLS or non-TLS stats and not
tied to the scheme. I recommend breaking up TLS and non-TLS metric and
calling them proxy.process.ssl. and proxy.process.non-ssl.
Good point. I didn't
Hi all,
just a reminder that we’re having an information meetup / hackathon in Tokyo in
November, at the Apple offices. More details at
https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=TS&title=QUIC+Hackathon+Fall+2018
This is open for everyone, the focus will be on QUIC,
I didn’t think about ipv4 and ipv6. If we want to break out all the stats so
you can figure out any combination we would need to have a stat hierarchy such
as: proxy.transport.process.encryption.http_version.scheme (e.g.
proxy.process.{ipv4,ipv6}.{tls,non-tls}.{http1,http2}.{http,https}).
The
1. To log asynchronously can't we use the existing logging code that logs
asynchronously the transactions?
2. Logging inline may produce the messages in order, but wouldn't it cause
heisenbugs?
3. It looks like the current developers/committers don't know whether
logging lnline was intentional or a
> On Oct 17, 2018, at 10:26 AM, Bryan Call wrote:
>
> I didn’t think about ipv4 and ipv6. If we want to break out all the stats so
> you can figure out any combination we would need to have a stat hierarchy
> such as: proxy.transport.process.encryption.http_version.scheme (e.g.
> proxy.pro
1) It might be possible but as noted I'm not sure it wouldn't invalidate
the utility of the logging messages.
2) Yes, it does. Again, it's a matter of which is the lesser evil. I think
synchronous writing for debug messages is the least worst choice.
3) I think it was deliberate.
The current TSVConnReenable() only takes a VConn as an argument. The two
other Reenable calls, TSHttpSsnReenable and TSHttpTxnReenable take an
object (Txn or Ssn) and a TSEvent as arguments. The event lets the plugin
signal back to the core whether its processing was successful or not.
I propose
Hi,
I am looking at the hostdb configuration and I need some clarification on
the configuration. In particular I have questions about these two
configuration parameters.
proxy.config.hostdb.host_file.path
proxy.config.hostdb.strict_round_robin
I am trying to understand how hostdb round_robin conf
> Also don’t forget that QUIC will have to get into the mix here, and long
term, both H2 and QUIC on the outbound connections.
Yah, and QUIC would have some versions (some features are already pushed
out from the first version). This brings up one more question; Should we
also think about TLS vers
