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
Considering that there's support for regex, it could be possible to have a domain that matches multiple domains in the configuration file. What happens in that case?
seems to indicate only the first traversed route which has a domain matching the domain will be returned.
Is the serdes guaranteed to always return the data in a reproducible manner (ideally top to bottom as in the config file?)
is iter() guaranteed to always iterate over the data generated by serdes in a reproducible manner (ideally same order as the data generated by serdes)?
If it is to be documented, maybe a test would be a nice thing to have as well?
A use case could be:
have a specific subdomain in one route, e.g. "my.example.com" -> backend:address = "10.10.10.10:443"
have all other subdomains in a default route, e.g. "*.example.com" -> backend:address = "11.11.11.11:443"
Note that I do not have a use for this right now, but just thought of it while reading through the denylist where it could make sense to have a denylist for one (or several subdomains) but not by default. (Or vice-versa).
The text was updated successfully, but these errors were encountered:
Considering that there's support for regex, it could be possible to have a domain that matches multiple domains in the configuration file. What happens in that case?
sniproxy/src/config.rs
Lines 97 to 99 in b16180e
seems to indicate only the first traversed route which has a domain matching the domain will be returned.
If it is to be documented, maybe a test would be a nice thing to have as well?
A use case could be:
Note that I do not have a use for this right now, but just thought of it while reading through the denylist where it could make sense to have a denylist for one (or several subdomains) but not by default. (Or vice-versa).
The text was updated successfully, but these errors were encountered: