Re: forward bumped traffic to parent in plain form

On 2026-04-16 07:41, Anthony Pankov wrote:

>> Alex: AFAICT, according to SslPeekAndSplice, after step1, Squid interprets "bump" as
>> * "talk to the server and then respond to the client" rather than
>> * "respond to the client and then talk to the server".


> If a bump after step1 defined as "talk to the server and then respond
> to the client" consequently Squid should not allow any "client-first"
> modes.

Today, Squid probably does not support "respond to the client and then 
talk to the server" behavior after step1. Assuming that is true:

* That current code state does not imply that Squid "should not" support 
such behavior in the future.

* It implies that if Squid gains such support in the future, then that 
support is likely to require changes in how Squid configuration is 
interpreted, probably either by adding new actions (to preserve behavior 
of existing deployments) or allowing the existing "client-first" action 
beyond step1 (with a risk of breaking a few existing deployments that 
still use that currently deprecated action).

Since I assume that the behavior you need does not match any existing 
configuration, I recommended hard-coding the new behavior as the next 
development step, and then, if you want to make those tested/working 
changes official, discussing how to make those hard-coded changes 
configurable. Alternatively, you can make all those configuration 
decisions upfront, making collaboration more difficult and increasing 
the risk that your configuration changes will be misunderstood and/or 
rejected.

Alex.

> Otherwise term "bump" in configuration must be redefined or have to
> be interpreted conditionally.