- This topic is empty.
-
Posts
-
BlackjackInfo wrote:Rest assured, a pipe character is just a regular old set of 8 bits, and it’ll be delivered just as reliably as any other set of 8 bits, whether you send ’em in pairs or solo. |||||||||||||| wheeee!!! Did they all get there?
This is the most idiotic statement I have ever read. It demonstrates the vacant knowledge you actually have. Give me the correct answer 15 pages why these are not good. Go ahead put your reputation on the line for a while seeing you never do. Perhaps try helping out some people receiving spam emails.
http://www.casinoaffiliateprograms.com/bb/showthread.php?p=101986#post101986
This is not the Internet but rather the Web. Now this really screws me up I will correct you the two are distinct.
Come on only asking for 15 pages. For the incorrect answer search google. For the right one search the jargon files. I am off this forum until you own up.
greek39
The packets will not be lost due to || characters. I certainly have written enough programs which process packets in various forms and sizes. That is just not how the transport layers confuse things.
The problem, lest we get off track here…. Is that Referback is likely NOT reconstructing the encoded urls properly, so this is the reason the tracking could be off… I seriously doubt that Referback takes the ‘LSS=JPCTYPEINTRAFFIC’ and converts it back to an affiliate tag. That makes no sense when the packet contains the typeintraffic tag.
They need to fix this and stop giving us a bunch of rubbish like we are all a bunch of idiots.
I know nothing of coding I will leave that to you gentlemen but this statement I can agree with…
They need to fix this and stop giving us a bunch of rubbish like we are all a bunch of idiots.
Uresk Links Pro fits the average need nicely, short SE friendly links, geotargeting if you want and quick at it’s job:
http://www.uresk.net/uresklinks.phpI switched to it after my old tracking program developed vulnerabilities after server upgrades and Uresk filled the slot niceley.
There seems to be a lot of avoidable argument going on here. Create a link, use a tracker and test it. They say you got 5 clicks, you say you got 5 clicks all is well in the world.
The pipe character will get there, all right. If anything, it’s only lower ASCII (below 32) which could be problematic, plus a few reserved characters.
The problem with using a character like a pipe, however, is that much depends on how the programmers are reading/storing/parsing the variables which contain these characters. I haven’t checked to see how these characters arrive in a POST or a GET, or whether any function is required to decode urlencoded strings… but my assumption is that one would be required to urldecode the returned variable as well.
Thus, if IE automatically urlencodes any of the strange characters it finds, but the original link was not urlencoded by the programmer, it is reasonable to assume that the programmer also did not use urldecode to receive the data because he didn’t encode it in the first place.
In a situation like this, it is highly likely that the variable will contain invalid data – which probably results in the default “TYPEIN” being set… and so an affiliate will lose the referral.
Of course, a URL which does not have characters requiring urlencoding will not have this problem – so why construct the link with these characters in the first place?
Referback may not intentionally have done this, of course – but they need to resolve this issue by removing the strange characters to ensure compatibility across all browser platforms and versions. For the record, IE6 displays the links correctly without modification. IE7 automatically urlencodes the link.
BTW, Partnerlogic uses a single pipe in their URLs – and IE7 does *not* urlencode the single pipe.
Good points Spear. The chance of a coding error or oversight in this situation is increased by the use of these characters. We have enough trouble with “&” vs “&” Now we have to worry about auto-urlencoding as well. Ugh.
LOL.
Thank goodness & is generally recommended (though not usually required) for HTML, not usually in URL construction
URLs are plenty complicated enough already. Lots of news sites use stuff like pipes and undecipherable strings of code – but they don’t have to worry about tracking affiliate referrals…
Spearmaster wrote:Referback may not intentionally have done this, of course – but they need to resolve this issue by removing the strange characters to ensure compatibility across all browser platforms and versions.Are we to think for one moment that their technical team is that inept? How do you muster up enough trust at any other level thinking as such? I would rather presume they know exactly what they are doing and pass it off as intentional. No less trust for sure, but it makes for sounder business sense.
I plead no contest Blackjack, I apologize. I won’t involved myself in these sorts of issues. No hard feelings just needed to chill. But I do like Axl’s comment!
greek39
axl wrote:Are we to think for one moment that their technical team is that inept? How do you muster up enough trust at any other level thinking as such? I would rather presume they know exactly what they are doing and pass it off as intentional. No less trust for sure, but it makes for sounder business sense.I’m not the biggest fan of Referback, as many of you already know. However, IE6 is still the norm, and the problem doesn’t occur in that version. It is entirely possible that the work they have been doing on the links was not done with IE7 in mind, not to mention that they may not have had anything to test with.
That being said, I still don’t see any place for pipes or other unusual characters in an URL. The sensible thing would be to ask Referback to remove that type of coding immediately, rather than harp on about whether or not this was intentional. Especially as it won’t be long before IE7 becomes the norm.
In the meantime, do as I have recommended many times in the past – either use their standard URLs without the double pipes – or remove them altogether until they fix this issue.
Spearmaster wrote:It is entirely possible that the work they have been doing on the links was not done with IE7 in mind, not to mention that they may not have had anything to test with.That being said, I still don’t see any place for pipes or other unusual characters in an URL. The sensible thing would be to ask Referback to remove that type of coding immediately, rather than harp on about whether or not this was intentional. Especially as it won’t be long before IE7 becomes the norm.
Exactly. And IE7 seems to have all problems ironed out and will be distributed through auto updates so it’s time now to do something.
I always thought that having this many special characters in their urls was slightly suspect. I went with the standard url – just one ? to pass the aff ID that´s all that is needed as the bare minimum.
Spearmaster wrote:That being said, I still don’t see any place for pipes or other unusual characters in an URL. The sensible thing would be to ask Referback to remove that type of coding immediately, rather than harp on about whether or not this was intentional. Especially as it won’t be long before IE7 becomes the norm.In the meantime, do as I have recommended many times in the past – either use their standard URLs without the double pipes – or remove them altogether until they fix this issue.
They have to remove all the marketing banners/text-links so new affiliates don’t use them and modify their functions to pase the questionable string correctly (for existing sites still using them) and then check it all for cross browser compatibilty.
I always check code with multiple browsers. If I remember correctly, the problem with IE is you can’t have two different versions installed at the same time unlike the other browsers.
