[BUG] Reverse Proxy Headers UI - Invalid value

[tgregory86]

What happened?

When configuring reverse proxy headers on a services in the UI, the UI reports that that values are invalid and will not allow you to save the config.

How to reproduce?

Configure reverse proxy headers in the UI as directed in the Docs. I have tried different combinations of values and they all report "invalid value"

Configuration file(s) (yaml or .env)

n/a

Relevant log output

n/a

BunkerWeb version

1.5.11

What integration are you using?

Docker

Linux distribution (if applicable)

Ubuntu Server 24.04

Removed private data

• I have removed all private data from the configuration file and the logs

Code of Conduct

• I agree to follow this project's Code of Conduct

[scetu]

Just saw this issue today, WebUI does accept comma instead of semicolon, but then NGINX on backend will throw an error because it accepts semicolon.

2024/11/19 09:32:26 [emerg] 4521#4521: invalid number of arguments in "proxy_set_header" directive in /etc/nginx/site.example.org/server-http/reverse-proxy.conf:36

This happens for most fields in WebUI for Reverse Proxy.

[TheophileDiot]

Hi @tgregory86, thank you for opening this issue.
Here's the regex for the setting with working examples: https://regex101.com/r/L8xGSj/1

[tgregory86]

I understand now, you need to leave off the last semicolon, since its automatically appended to the config.

[jujugoboom]

I just stumbled across this and after looking at the regex, I'm not sure it handles input as expected. The lookaround (?!.*\2 ) causes some headers to need specific ordering to be able to set (you can't do Host $host; X-Forwarded-Host $host but you can do X-Forwarded-Host $host; Host $host)