We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From Nginx perspective any of next two constructions is valid:
A.
add_header Strict-Transport-Security "max-age=0; includeSubDomains" always;
B.
add_header Strict-Transport-Security " max-age=0 ; includeSubDomains " always ;
But both ones can't be parsed correctly.
The text was updated successfully, but these errors were encountered:
See no options for now other than to roll back these PRs:
#18 #20
And use https://github.com/nginxinc/crossplane tool to get "normalised" input config:
crossplane parse --indent=4 --combine /etc/nginx/nginx.conf > nginx_crossplane_parse.json PYTHONIOENCODING=UTF-8 crossplane build --stdout nginx_crossplane_parse.json > nginx_crossplane_build.conf
It would eliminate both multi-line blocks and multiblok lines.
The Nginx crossplane tool has portings to Go and Ruby - not to JS so for.
Sorry, something went wrong.
fix(parser): split lineRaw into multiple lines separated by each semi…
a9f4779
…colon fix [webantic#22](webantic#22)
919fb1b
…colon (#23) fix [#22](#22)
No branches or pull requests
From Nginx perspective any of next two constructions is valid:
A.
B.
But both ones can't be parsed correctly.
The text was updated successfully, but these errors were encountered: