8000 [nginx_parser] WARNING Skip unparseable block: "http" · Issue #103 · yandex/gixy · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[nginx_parser] WARNING Skip unparseable block: "http" #103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Open
Frodox opened this issue Sep 17, 2019 · 0 comments
Open

[nginx_parser] WARNING Skip unparseable block: "http" #103

Frodox opened this issue Sep 17, 2019 · 0 comments

Comments

@Frodox
Copy link
Frodox commented Sep 17, 2019

Gixy v0.1.20 failes with message [nginx_parser] WARNING Skip unparseable block: "http"
on config like

    log_format json escape=json ''
        '{ "@timestamp": "$time_iso8601", '
...
# problem line:
        '"any_variable": "any-value", ' # header "Location" received from upstream (in case of redirect)
...
        '"upstream_status": "$upstream_status" '
        '}';

and after tests:

# gixy -d nginx.conf
[main]	DEBUG	logging initialized
[manager]	DEBUG	Audit config file: /etc/nginx/nginx.conf
[nginx_parser]	WARNING	Skip unparseable block: "http"

==================== Results ===================
No issues found.

==================== Summary ===================
Total issues:
    Unspecified: 0
    Low: 0
    Medium: 0
    High: 0

if I using line like '"any_variable": "any-value", ' # header "Location" received from upstream in case of redirect
or
'"any_variable": "any-value", ' # header "Location" received from upstream (redirect)

all works fine.
Problems with parser:

  • it parses comments (but it shouldn't)
  • it failes to parse comment like (two or more words in braces)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Frodox
0