This topic contains 8 replies, has 1 voice, and was last updated by chanet 4 months, 3 weeks ago.
- July 20, 2018 at 3:15 pm #4709
I’ve got quite a lot of adult affiliate links that seems to redirect from http to https.
Is it safe in general to update the link i use to have https?July 20, 2018 at 3:17 pm #4710
It’s better because it avoids a useless 302 (or 301 can’t remember) redirect. On the other side if the site linked for some reasons drops HTTPS and you are linking it “natively” with HTTPS you can end up with an error page instead of paysite.July 20, 2018 at 3:18 pm #4711
This is a good point, but in this day and age with google pressing sites to have https I see it as unlikely any site worth their salt removing https… But as jonvryant says the less redirects the better, as I always myself see redirects as a “potential for error” and the more there is the higher the potential for something to change something and for things not to work.
That being said… I know its a complete pain in the ass, but I would speak to each paysite/network directly, as some may be testing HTTPS versions of their sites without the intention of keeping it should they find too many errors, as happened with me and one of my links recently for another paysite.July 20, 2018 at 3:20 pm #4712
Fishy installed SSL on a couple of our adult sites for testing previously (3 months ago) and all has gone well. He is now in the process of installing SSL on the rest of our sites and partner sites with the exception of “dead” sites (no longer updating).
At this point, he is redirecting. To date, we have not seen any problems “with or for” our affiliates. IF we run into something that “will cause or causing” issues for affiliates, I will be sending out a newsletter. Otherwise, it’s business as usual.July 20, 2018 at 3:21 pm #4713
I wrote a script to figure out if it was safe to change. Feel free to use it…
Put in your jump script URL and it will show you if HTTPS is supported at every step. If HTTPS is supported at every step, then it’s safe to switch. It also reports when cookies are set, highlights known affiliate cookies, etc.
If it seems to hang, it means it’s not working (usually that means HTTPS isn’t set up). Trying the same URL over again will almost certainly not produce a different result. Click “don’t check HTTPS” and try again.
And please use it manually – don’t have an automated tool throw a lot of URLs at it. Don’t try CCBill links. They don’t work.July 20, 2018 at 3:25 pm #4714
best to test a ccbill http link to see if it tracks your affiliate account through to the join if you change the link to https.July 20, 2018 at 3:29 pm #4715
Is it possible to check CCBILL cookie length with this script? I mean clicking “Don’t check HTTPS” before checking a CCBILL link code. I tried with a few CCBILL links. The result shows something like 0.7 day cookie, 2.7 day cookie or 29.7 day cookie… So it can also be used to check CCBILL cookie length?July 20, 2018 at 3:31 pm #4716
If it’s saying 0.7, 2.7 and 29.7 – then that’s the length of the cookie. Cookies are set in seconds, not full days, so fractional days are completely possible.
If those are the lengths you’re seeing then the CCBill server is subtracting 0.3 days (~7 hours) from each cookie. That’s most likely their GMT offset so they have a bug in their code that’s using local time rather than GMT when setting cookies, hence all cookies are 7 hours shorter than they’re supposed to be. So the sponsor asked for a 1, 3 and 30 day cookie and CCBill set something 7 hours shorter than requested.July 20, 2018 at 3:34 pm #4717
Right. I wasn’t clear about that. The script works fine for CCBill as long as you don’t have it check HTTPS. It will fail if you try to check HTTPS.