I'm using a report action to go to URL with reference to a second report including passing a text parameter.
This parameter can include different kinds of spacial characters such as &, ™, £, , ?, !, etc.
I need to escape them. The UrlEncode function I found is not working for me. I need to use such a function but I'm not sure how to create one in SSRS.
I couldn't find anything else on the web, all articles I did find relate to encoding and not to decoding...
I need to parse a URL string like this one:
I need to split the NSString up into the signle parts like
&avg_rating=4.82280613104. I've been doing this with
substringWithRange: but the values return in a random order, so that messes it up. Is there any class that allows easy parsing where you can basically convert it to NSDictionary to be able to read the value for a key (for example ValueForKey:
cid should return
241). Or is there just another easier way to parse it than using
NSMakeRange to get a substring?
I am trying to style an rss feed using xslt. I want to display an image that is stored in the tag on the feed. The problem is it is encoded to display as text on the page instead of being rendered. The following is an example of part of the string.
1). <description><img src="http&#58;&#47;&#47;buavhw.blu.livefilestore.com&#47;y1ppCokLxFJSG2cmyPdvg...
I had to add extra coding to the string above to get it to appear properly here. The string below is how it appears when I paste it directly into the text box.
2). <description><img src="http://buavhw.blu.livefilestore.com/y1ppCokLxFJSG2cmyPdvg...
If I copy and paste it again from the preview window it only then becomes the following string.
3). <description><img src="http://buavhw.blu.livefilestore.com/y1ppCokLxFJSG2cmyPdvg...
[This may not be precisely a programming question, but it's a puzzle that may best be answered by programmers. I tried it first on the Pro Webmasters site, to overwhelming silence]
We have an email address verification process on our website. The site first generates an appropriate key as a string
It then encodes that key as a bunch of bytes
It then base64 encodes that bunch of bytes
Since this key is going to be given as a querystring value of a URL that is to be placed in an HTML email, we need to first URLEncode it then HTMLEncode the result, giving us (there's no effect of HTMLEncoding in the example case, but I can't be bothered to rework the example)
This is then embedded in HTML that is sent as part of an email, something like:
click <a href="http://myapp/verify?key=JiRkYWN%2ByoyIhIQ%3D%3D">here</a>. Or paste <b>http://myapp/verify?key=JiRkYWN%2ByoyIhIQ%3D%3D</b> into your browser.
When the receiving user clicks on the link, the site receives the request, extracts the value of the querystring 'key' parameter, base64 decodes it, decrypts it, and does the appropriate thing in terms of the site logic.
However on occasion we have users who report that their clicking is ineffective. One such user forwarded us the email he had been sent, and on inspection the HTML had been transformed into (to put it in terms of the example above)
click <a href="http://myapp/verify?key=JiRkYWN+yoyIhIQ%3D%3D">here</a>Or paste <b>http://myapp/verify?key=JiRkYWN+yoyIhIQ%3D%3D</b> into your browser.
That is, the %2B string - but none of the other percentage encoded strings - had been converted into a plus. (It's definitely leaving us with the right values - I've looked at the appropriate SMTP logs).
So I think that there are a couple of possibilities:
There's something I'm doing that's stupid, that I can't see, or
Some mail clients convert %2b strings to plus signs, perhaps to try to cope with the problem of people mistakenly URLEncoding plus signs
In case of 1 - what is it? In case of 2 - is there a standard, known way of dealing with this kind of scenario?
Many thanks for any help
Previously, I was able to find out where my Outbrain traffic was coming from because they included a URL param "origSrc=1534129" (which is FoxNews.com) in the referrer like this:
They recently encoded their URLs and they now look like this (taken from a module on FoxNews):
Somewhere in those four URLs is a param that identifies the site as FoxNews.com or an origSrc id.
Does anyone know how to find out what the origSrc is in the new URLs?