Skip to content

Fix the ability to use ; in config values - #4653

Merged
nickva merged 1 commit into
mainfrom
fix-comment-parsing-in-config
Jun 22, 2023
Merged

Fix the ability to use ; in config values#4653
nickva merged 1 commit into
mainfrom
fix-comment-parsing-in-config

Conversation

@nickva

@nickva nickva commented Jun 22, 2023

Copy link
Copy Markdown
Contributor

Config values may contain ; in them as long as ; is not preceded by a space or a tab character.

Fixes: #4651

This regression was introduced in: #4287

Config values may contain `;` in them as long as `;` is not preceded by a
space or a tab character.

Fixes: #4651
@mohmesflir

Copy link
Copy Markdown

The string of ; separated values that I have been using do not have a space or tab preceding the ;. So this is not working in 3.3.x.

@mohmesflir

Copy link
Copy Markdown

It does work in versions prior to and including 3.2.3 but not in 3.3.1 or 3.3.2

@rnewson rnewson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops

@nickva

nickva commented Jun 22, 2023

Copy link
Copy Markdown
Contributor Author

The string of ; separated values that I have been using do not have a space or tab preceding the ;. So this is not working in 3.3.x.

That makes sense. The PR should fix it. If you're able to compile and make release yourself let us know if it work.

Thanks for reaching out and reporting the issue.

@nickva
nickva merged commit fafa982 into main Jun 22, 2023
@nickva
nickva deleted the fix-comment-parsing-in-config branch June 22, 2023 21:15
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.

csp header parameters require semicolon separated list but seen as comment in .ini file

3 participants