Greg Wilkins

@joakime can you describe a bit more what this issue is about? If I look at `Handler.Sequence` I see: ```java @Override public InvocationType getInvocationType() { if (isDynamic()) return InvocationType.BLOCKING; InvocationType...

> Hello - any plans about this one? Yes - we will be looking in the next week or two, as we plan to release 12.1.0 next month

@janbartel I can't see anything wrong in the implementation of welcome servlets. See #12982 for improved testing and clarified documentation. If you think there is still something wrong, can you...

@joakime I'm wondering if just a rule would be good enough. A rule would just correct forever. If it was put in a handler, then it could have more nuanced...

I think you have answered your own question. It is a case insensitive cache of common header values. There are compliance modes that you can use to bypass the cache...

@gjoshi86 The cache is indeed an optimization to avoid many copies of the same string being created and also to allow fast lookup of the actual semantics. For fine grained...

@joakime why is this not closed? @sbordet doesn't the dump cycle protection introduced in the PR resolve this generally?

@joakime rather than setting "canonicalizing" and "decoding" on the rule, perhaps just set a ComplianceViolation.Mode on it and it can decide to canonicalize and/or decode by looking at the violations...

My 2c is that: + `core-deploy` becomes `coreapp-deploy`, as it deploys `CoreAppContext`s + `core` env stays as `core` as it can deploy coreapps or core components + `StatisticsContextHandler` is a...

I've moved the javadoc changes to #13212 so they can get merged quickly.