You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, such behavior is implemented for the actual tests using the config field testoverride.input.headers of type map. Per my tests, these custom request headers are not used in the logmarker requests.
Considering the same configurability for the logmarker requests and extending its config API with this feature, makes it more flexible and avoids potential unnecessary logic customization or configuration on the custom WAF servers side.
If I'm missing any point here, I'd appreciate your clarifying it.
Thanks.
The text was updated successfully, but these errors were encountered:
Hi,
Currently, such behavior is implemented for the actual tests using the config field
testoverride.input.headers
of type map. Per my tests, these custom request headers are not used in the logmarker requests.Considering the same configurability for the logmarker requests and extending its config API with this feature, makes it more flexible and avoids potential unnecessary logic customization or configuration on the custom WAF servers side.
If I'm missing any point here, I'd appreciate your clarifying it.
Thanks.
The text was updated successfully, but these errors were encountered: