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
as I do not care to invest the time to discover the other potential domains subdelegated to the mm.bing.net zone: that is I do not want to be forced to
Case two might more clearly highlight the need for fractionalized subdoamins -- assuming you offer '*' for multiple characters and '?' for single character
While the proposed wildcard characters "" and "?" are excluded by RFC from the host and domain name, it should be noted that RFC explicitly permits for special characters (eg "") in URLs.
This should be a consideration if full URL specificity ([comment:3:ticket:7 #7 comment 3]) is implemented.
re: AMO / wildcard subdomains for full domain mode please
re: ticket #8
I would prefer
sub_.domain.tld
sub.sub_.domain.tld
sub?.domain.tld
in addition to / as opposed to
*.sub.domain.tld
example sites:
[1]
bing images
http://www.bing.com/images/search?q=unicorn+power&FORM=BIFD
[2]
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
[3]
http://www.bing.com/maps/
allow from imageshack.us to *.imageshack.us
http://img37.imageshack.us/img37/7712/simplecase.png
I would want
allow from www.bing.com to ts*.mm.bing.net
as I do not care to invest the time to discover the other potential domains subdelegated to the mm.bing.net zone: that is I do not want to be forced to
allow from www.bing.com to *.mm.bing.net
I would want
http://img97.imageshack.us/img97/9688/case2.png
allow from technet.microsoft.com to i?.technet.microsoft.com
this would not allow i.technet.microsoft.com, but only i2, i3, and i4 (as it is currently) but potentially through i9
http://img710.imageshack.us/img710/1577/case3.png
allow from www.bing.com to ecn.t*.tiles.virtualearth.net
as I'm not sure if
allow from www.bing.com to t_.tiles.virtualearth.net
implies
allow from www.bing.com to *.t_.tiles.virtualearth.net
SW
The text was updated successfully, but these errors were encountered: