Attributes are dismissed in config file
Robot-DaneelOlivaw opened this issue · comments
As per https://github.com/v2ray/domain-list-community#attributes, I tried geosite:baidu@ads
, geosite:google@ads
and geosite:steam@cdn
in config file:
{
"type": "field",
"domain": [
"geosite:baidu@ads",
"geosite:google@ads"
],
"outboundTag": "blocked"
}
or
{
"type": "field",
"domain": [
"geosite:steam@cdn"
],
"outboundTag": "direct"
}
V2Ray returned v2ray.com/core/app/router: this rule has no effective fields
. All of them were dismissed, not even taken as geosite:baidu
or geosite:steam
(geosite:google-ads
hasn't been tagged). Although geosite:baidu-ads
and geosite:google-ads
still worked. I wonder whether this function has been deployed or am I just doing it wrong?
V2Ray returned v2ray.com/core/app/router: this rule has no effective fields.
@Loyalsoldier In fact, I test with geosite:adcolony-ads@ads
, core return a same error.
adcolony-ads' content:
adcolony.com @ads
Neither
baidu
has@ads
attr inside. Don't work definitely. The one(google) in README just an example.
You're right. But they do exist in baidu-ads
which is included in baidu
.
I test with
geosite:adcolony-ads@ads
, core return a same error.
Maybe this function hasn't been deployed at all.
Don't know if it is a bug for now. I would like to read the source code of V2Ray's router package soon. Still don't know whether I can figure it out. Or you can file an issue in v2ray-core
project to draw attentions to help you with this.
@Loyalsoldier I found a commit that describes the syntax of this README and the date of submission is December 8, 2018.
See 8b28f90.
If you are going to look at the source code of the router
, this date may be of some help to you.
Close. Fixed in v2fly/domain-list-community#79.