Optional HTTP header allowed?

[sn1p3rt3s7]

Hi,

I am encountering an issue while using katana for a subdomain.
The problem is some endpoint return 400 when CSRF header is added while some request need that.
katana -headless -u https://booking.example.com -cwu ws://127.0.0.1:9222/devtools/browser/{value_123} -no-incognito -H 'booking_functionality_header_list' -cos logout

Is there already an option, if not could you please add a feature.
For e.g. headers starting __ will be considered as optional where it is used first if getting an error status code then remove the header.