new port-search wildcarding - bad idea?
* for an exact match use "quoting", a bit like what Google does to enforce a search term * otherwise terms are assumed to be wildcard bounded and case insensitive * without quotes, * and ? characters are supported for multi and single character wildcards. we could revert this commit if we don't like it.
This commit is contained in:
@@ -14,13 +14,13 @@
|
||||
<tr>
|
||||
<td class="nd_center-cell">[% row.left_dns || row.left_ip | html_entity %]</td>
|
||||
<td class="nd_center-cell"><a class="nd_linkcell"
|
||||
href="[% device_ports %]&q=[% row.left_dns || row.left_ip | uri %]&f=[% row.left_port | uri %]&c_duplex=on">
|
||||
href="[% device_ports %]&q=[% row.left_dns || row.left_ip | uri %]&f=%22[% row.left_port | uri %]%22&c_duplex=on">
|
||||
[% row.left_port | html_entity %]</a></td>
|
||||
<td class="nd_center-cell">[% row.left_duplex.ucfirst | html_entity %]</td>
|
||||
|
||||
<td class="nd_center-cell">[% row.right_dns || row.right_ip | html_entity %]</a>
|
||||
<td class="nd_center-cell"><a class="nd_linkcell"
|
||||
href="[% device_ports %]&q=[% row.right_dns || row.right_ip | uri %]&f=[% row.right_port | uri %]&c_duplex=on">
|
||||
href="[% device_ports %]&q=[% row.right_dns || row.right_ip | uri %]&f=%22[% row.right_port | uri %]%22&c_duplex=on">
|
||||
[% row.right_port | html_entity %]</a></td>
|
||||
<td class="nd_center-cell">[% row.right_duplex.ucfirst | html_entity %]</td>
|
||||
</tr>
|
||||
|
||||
Reference in New Issue
Block a user