Using the API to search for a hash in an SSID
Hi
Not sure if this is a bug in the API or im using it wrong... but if you try to do a search via the API for an SSID (netid) that starts with a hash for example '#Passpoint' then it returns way more data than it should, I see netid's that dont match that so assuming its the hash somehow?
Am I using it wrong?
Any advice
Many thanks
Chris
Not sure if this is a bug in the API or im using it wrong... but if you try to do a search via the API for an SSID (netid) that starts with a hash for example '#Passpoint' then it returns way more data than it should, I see netid's that dont match that so assuming its the hash somehow?
Am I using it wrong?
Any advice
Many thanks
Chris
Posting a reply to my own issue, in the vague hope it helps others, through trial and error and reading about # it would appear anyone doing the same as me, needs to swap the # for %23
So instead of searching with for example "#Passpoint" try "%23Passpoint" (without the quotes) when using the API
Problem Solved![Smile :-)](./images/smilies/icon_smile.gif)
Have a great day.
Chris
So instead of searching with for example "#Passpoint" try "%23Passpoint" (without the quotes) when using the API
Problem Solved
![Smile :-)](./images/smilies/icon_smile.gif)
Have a great day.
Chris
sounds like you found the answer, but yes, url-encoding applies!
cheers, and thanks for your interest!
-ark
cheers, and thanks for your interest!
-ark
Who is online
Users browsing this forum: No registered users and 44 guests