You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dump files still saved server which is comment at serverlist file.
when server list file is:
#server s1:8081 weight=50 max_fails=2 fail_timeout=3s;
server s2:8081 weight=50 max_fails=2 fail_timeout=3s;
server s3:8081 weight=50 max_fails=2 fail_timeout=3s;
I see dump in server which has nginx-upstream-serverlist moudle:
server s1:8081 weight=50 max_fails=2 fail_timeout=3s;
server s2:8081 weight=50 max_fails=2 fail_timeout=3s;
server s3:8081 weight=50 max_fails=2 fail_timeout=3s;
is this right ? all server list file must return some header?
The text was updated successfully, but these errors were encountered:
The parser of serverlist in the module is not as strict as the nginx's conf parser.
So the comment symbol "#" is ignored by the parser. In other words, "#server s1:8081 weight=50 max_fails=2 fail_timeout=3s;" is equal "server s1:8081 weight=50 max_fails=2 fail_timeout=3s;".
It is ugly, but just work. I will polish this in the future.
dump files still saved server which is comment at serverlist file.
when server list file is:
I see dump in server which has nginx-upstream-serverlist moudle:
server s1:8081 weight=50 max_fails=2 fail_timeout=3s;
server s2:8081 weight=50 max_fails=2 fail_timeout=3s;
server s3:8081 weight=50 max_fails=2 fail_timeout=3s;
is this right ? all server list file must return some header?
The text was updated successfully, but these errors were encountered: