-
Notifications
You must be signed in to change notification settings - Fork 151
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.
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
cant get upstream.current_upstream_name to work #39
Comments
@amgorb Please provide a minimal and standalone example that we can easily run and reproduce the problem on our side. Thank you. You can check out the test suite of this module for examples of "minimal and standalone" test cases. |
@amgorb Your example above is incomplete since there lacks definitions for things like |
i was able to reproduce problem with config below:
|
@amgorb You know that your Your
|
I am using php-fpm and I am also hitting this same issue .. I am not sure exactly WHEN current_upstream_name is going to be available for use? I would assume that body_filter is AFTER everything has processed, and theoretically the upstream should be initialized by this point? Perhaps there is a different upstream for php-fpm? I am getting:
I am doing the following in my nginx config at the bottom of my server block after everything:
|
tried different variants of configuration, no change
config:
$upstream_name used in log_format
expect to see upstream name (_bk_api_common) in logs but got 'test' string and following in error.log:
upstreams are working fine.
What can cause 'no srv conf for upstream' error?
The text was updated successfully, but these errors were encountered: