LBS feature request: implement wildcards in parts of domain names |
||||
Issue descriptionSummary: in the page https://support.google.com/chrome/a/answer/3062039 is written: "Host-name part: Specify complete domain names like "www.example.com" or parts of domain names like "example.com” or even "example". Use this to open entire sites with your legacy browser, such as your intranet. Wildcards are not supported yet for parts of domain names." Use case / Motivation: the customer has many different hosts to open in chrome and they want to be more precise possible, they have tried: http://*.example.local/testlogin/sslogin.html http://example.local/testlogin/sslogin.html but it's not working Existing workarounds: expand the list of hostnames, for example: http://host1.example.local/testlogin/sslogin.html http://host2.example.local/testlogin/sslogin.html http://host3.example.local/testlogin/sslogin.html http://host4.example.local/testlogin/sslogin.html ... http://hostz.example.local/testlogin/sslogin.html Case#: 16435303
,
Sep 5
,
Oct 22
,
Oct 22
For their use-case, is it possible to use just the hostname as a rule? A rule with no slash is treated as a domain name *substring*, not an exact match. e.g. the rule 'example.com' matches 'http://host1.example.com/'. However, the rule 'example.com/something' won't match 'http://host1.example.com/something'. This is because the rule contains a slash, and gets treated as a prefix. So, this may not fit their use-case depending on what they're doing.
,
Nov 12
marcore@chromium.org what do you think about workaround in comment #4? Can you check with the customer if this would work? |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Sep 4