Do you mean POST data? I log all HTTP headers, and I just looked at a couple of HTTP 301->HTTPS 200 sequences - all headers are preserved over the redirect, including the referer.

Google really sucketh dicketh. :2 cents:

i siwtched my site to https and traffic dropped 90% .
becuase google is stupid and treats http and https as 2 separate sites/entities. it takes time to get back to old position/rankings ...

lesson learned., https is not that important if you are not having members area or billing members.

majority top 10k alexa sites are still using http as preferred its not that they dont support https, but at least they are not doing 301 from http to https..

2 cents.

Problem for us is some sites we submit to, like the Hun have announced if you have not switched it may be a problem soon. If I understand their message correctly.

I submit to the HUN a lot and never received any notice from them on the https issue..Just went and check there rules again and I do not see anywhere in there about switching to https. Unless I'm not looking in the right place.

imho just enabling https doesnt hurt, but force redirecting one protocol to another does . i am talking about serp here and not direct traffic.

You realize HTTPS is now a form of SEO, right? Google favors HTTPS over non-HTTPS.

Has anyone made the transition from http to https: on Wordpress without any ranking drop? If so what plugin if any?

Thanks

The rankings for me go down, then come back up after re-indexing.

So I got the HTTPS proxy set up, which rewrites http:// references to go via the script (which is fetched via HTTPS) rather than the affiliate site (which is HTTP). The intent is to prevent the browser warning of insecure content, because my HTTPS page includes content from a HTTP URL.

Then I find that the affiliate program drops my refid from the HTML when my server fetches the content on behalf of the visitor, instead of the visitor's browser fetching it directly. My workaround does NOT work.

I've sent them 3 messages in the past 6 weeks and there's been no response.

Don't know whether to laugh, or cry. :Oh crap

With all of the spaghetti code in sponsors' backends for promotools -- updating to HTTPS/TLS can be a complex and lengthy process. We just did this a few months ago it was not easy.

Google may not even realize the mess they have created -- but what the fuck to they care? Google is in business to sell search ads and Android ad tracking systems.

Yeah, after having to mess around with dual HTTP/HTTPS functionality on my relatively small site, I do have an appreciation for how much of a headache it would be to add (AND properly test for all edge cases) HTTPS capability to a more complex setup.

Still doesn't excuse them ignoring affiliates. Years ago I had to resort to calling a number in their WHOIS entry just so they'd talk to me.

Well after the frustration with the affiliate program yesterday, have to give them props, we did manage to establish proper communication, and they've subsequently set up a new certificate to allow HTTPS to be used on the domain. Do have to do some testing to make sure that promo content still works as expected when delivered via HTTPS, but it looks good so far.

Of course this all happened after I had spent some time writing the custom HTTPS proxy. :disgust But I did manage to get that working, so my site including promo iframes is now 100% HTTPS and is no longer tainted with warnings about insecure content. My referred hit counts are already going back up.