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
From expanding the tests on the PR #618 we have found several issues with parse_nameservers function in the gateway/src/resty/resolver.lua file.
Identified Problems
The bellow expression will do not catch the case where server == resolver because the function to.string of the meta table resolver is concatenating "serverName_ip".."ServerNamePort"
ifserverandserver~=resolvertheninsert(nameservers, nameserver.new(server))
end
The parsing of search local.domain #foobar brakes the regex
Those are the identified cases I found that brakes the resolver. Maybe should extend a bit the test cases.
To Do:
correct server == resolver case
correct parsing search local.domain #foobar
The text was updated successfully, but these errors were encountered:
From expanding the tests on the PR #618 we have found several issues with
parse_nameservers
function in thegateway/src/resty/resolver.lua
file.Identified Problems
server == resolver
because the functionto.string
of the meta tableresolver
is concatenating"serverName_ip".."ServerNamePort"
search local.domain #foobar
brakes the regexThose are the identified cases I found that brakes the resolver. Maybe should extend a bit the test cases.
To Do:
server == resolver
casesearch local.domain #foobar
The text was updated successfully, but these errors were encountered: