Hot!Questions about URLfilter matching specifics

Author
SilverbackNet
New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2018/06/18 10:18:17
  • Status: offline
2018/06/18 10:52:19 (permalink) 6.0
0

Questions about URLfilter matching specifics

Hello, I've been tasked to normalize a chaotic, organically grown bunch of rules on several locked-down sites' FGT60E routers, but I do not have a test box and I must keep live testing to a bare minimum, so I have some questions about where the documentation is vague. This is a case where "." is blacklisted as the last entry, and all other sites are individually whitelisted.
 
Is there a difference between:
edit 1
set url "example.com"
set action allow
next

and
edit "example.com"
set action allow
next

? Do the numbers matter, or just the position?
 
Exactly what does "example.com" match, with the default "set type simple"? Will it match "www.example.com"? Is it strictly limited to the domain name, or anywhere in the URL? Will "google.com/search?q=example.com" match it? What about "example.com.fakesite.com"?
 
What about "*.example.com" with "set type wildcard"? Will "google.com/search?q=www.example.com" match it? Will "http://example.com" match it? (The latter seems doubtful unless a special rule was implemented for that case.)
 
If all of these are general URL matchers, rather than domain matchers, then it seems like anyone could bypass filtering by appending "?bypass=example.com" (for this example) to every URL. Is there any way to keep strictly limited to domains without having to make every entry a regex, like "https?://[^/]*example.com/"? Is the scheme even included?
#1

0 Replies Related Threads

    Jump to:
    © 2018 APG vNext Commercial Version 5.5