wallarm/api-firewall

Remote specs without custom header name

ingowalther opened this issue · 2 comments

ingowalther commented

Hello team,

if I specify the specs via a url and do not specify a value for “api-specs-custom-header-name”, an invalid header is built, which leads to an apache error 400.

Apache Log:
[Thu Sep 12 15:01:14.341376 2024] [core:debug] [pid 17:tid 17] protocol.c(1288): [client 172.27.0.9:58414] AH02426: Request header field name is malformed: :

[Thu Sep 12 15:01:14.341398 2024] [core:debug] [pid 17:tid 17] protocol.c(1481): [client 172.27.0.9:58414] AH00567: request failed: error reading the headers

The docker container only starts when I add the parameter APIFW_API_SPECS_CUSTOM_HEADER_NAME, even if I don't need it.

I also noticed that the environment variables are described incorrectly in the documentation (https://wallarm.github.io/api-firewall/installation-guides/docker-container/#step-4-configure-api-firewall). It says API_SPECS_CUSTOM_HEADER_NAME & API_SPECS_CUSTOM_HEADER_VALUE instead of APIFW_API_SPECS_CUSTOM_HEADER_NAME & APIFW_API_SPECS_CUSTOM_HEADER_VALUE

Greetings Ingo

afr1ka commented

Hello Ingo,

Thanks for the issue. Fixed in the v0.8.1

  • 👍1
ingowalther commented

Hello Nikolay,

I have tried version 0.8.1 and can also confirm that the bug has been fixed. 🎉
Thank you!

Greetings
Ingo