[
https://issues.apache.org/jira/browse/GUACAMOLE-820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871555#comment-16871555
]
Michael Jumper commented on GUACAMOLE-820:
------------------------------------------
Sure enough. The intent is there, but connection parameters are not searched,
nor are the parameters generally exposed until explicitly retrieved when a
specific connection is being edited. It may be that the IP address matching has
only ever had an effect when searching the usage history.
If we want to match against addresses in parameters, that needs to be
corrected. If matching against parameter contents can't reasonably be allowed,
filter behavior should be corrected such that searching for addresses behaves
more intuitively, even when those addresses are substrings within a connection
name.
> IP address filters do not match connection parameters
> -----------------------------------------------------
>
> Key: GUACAMOLE-820
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-820
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-client
> Affects Versions: 1.0.0
> Reporter: Nicolas CHARREL
> Priority: Minor
> Attachments: image-2019-06-19-17-11-43-136.png,
> image-2019-06-19-17-12-53-087.png
>
>
> Hello,
> All my connections are named "HOSTNAME - IP". By example "GUAC - 127.0.0.1"
> When I'm looking for this entry, I type in the filter 127.0.0.1 and I find
> nothing. But when I type 127.0.0. I find my entry.
> It's seems when I'm looking for a full IP there is a bug and the search
> always return empty list.
> First case (with 127.0.0), I find my connection:
> !image-2019-06-19-17-11-43-136.png!
>
> Second case (with all the ip), there is no answer:
> !image-2019-06-19-17-12-53-087.png!
> Thanks for your help !
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
