So I have a lookup table that consists of some URLS to other dashboards as well as other environment pages (the complete urls). I've coded a table to show the specific Application that the user has selected (from a separate input token). When the user clicks that row of the table, the user is supposed to be navigated to the url from the lookup table, but the url is altered in the browser the inclusion of different characters like "%" or 20's. Can someone please explain how to keep the browser from altering the exact url that I'm getting from the lookup table?
Thanks in advance
It sounds like you're seeing standard HTML URL encoding. For example %20 replaces a [space] character
www.w3schools.com/tags/ref_urlencode.asp
This is expected behavior and your urls may not even work if not for the encoding. For example type https://www.splunk.com/dog cat
into your browser bar. It will automatically encode as https://www.splunk.com/dog%20cat
I understand URL encoding and I also understand that it's what's changing the URL, but when I hardcode the URL into my sourcecode instead of use the lookup table value the URL stays exactly the same. I guess my question is, how do I use some sort of token/lookup table solution without having to hardcode the URL's without URL encoding altering it?
Currently (just to put a solution in place) I'm hardcoding most of the URL but adding a token to put the App context in place. Ex: app/itsi/dashboards
Where "itsi" is a token from my lookup table. I was hoping to simply have the whole URL in the lookup table cell and navigate to pages outside Splunk as well.