Skip to content

cache_req{,_fsm}: Add resp.storage control over synth body's storage#4358

Open
nigoroll wants to merge 1 commit intovarnishcache:masterfrom
nigoroll:sync_resp.storage
Open

cache_req{,_fsm}: Add resp.storage control over synth body's storage#4358
nigoroll wants to merge 1 commit intovarnishcache:masterfrom
nigoroll:sync_resp.storage

Conversation

@nigoroll
Copy link
Member

@nigoroll nigoroll commented Jul 8, 2025

draft PR of WIP for early review / feedback opportunities.

Next steps (planned, do not nail me down on this)


This adds the vcl variable resp.storage, available from vcl_synth {} to control which storage the synth response body gets created on.

Rather than just remembering the stroage for use after VCL has returned, we actually create an object on it when the variable changes.

This is the first step towards #4344

@nigoroll
Copy link
Member Author

Bugwash: Does Resp_l_storage() exist for a could reason or could we use just the VRT_ functions?

@nigoroll
Copy link
Member Author

Bugwash: Does Resp_l_storage() exist for a could reason or could we use just the VRT_ functions?

The answer is that we do not have a VRT_CTX in cnt_synth, because we only create it in the "fsm wrapper" VCL_*_method, but we need to call the "set the default storage" function from cnt_synth in case VCL has not set (or unset) the storage.

@nigoroll nigoroll marked this pull request as ready for review November 10, 2025 15:07
This adds the vcl variable resp.storage, available from vcl_synth {} to control
which storage the synth response body gets created on.

Rather than just remembering the stroage for use after VCL has returned, we
actually create an object on it when the variable changes.

This is the first step towards varnishcache#4344
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant