How change a site https to http?
-
I have two supplementary wordpress.com sites
http://onehourpraiseandworship.wordpress.com/
https://hymnstoenjoy.wordpress.com/
Now one is https and the other is http. I didn’t choose to make these like this. It just happened when I created them some time ago.
How can I change the second site into http (ie get rid of https)?The blog I need help with is: (visible only to logged in users)
-
On domains including “wordpress.com” both http and https will work. That means you can just drop the s and go straight to http://hymnstoenjoy.wordpress.com/
You shouldn’t need to get rid of the s though. Using https is generally better in most contexts.
-
WordPress.COM is in the process of changing all addresses over to https – it’s more secure and Google is starting to downgrade sites that do not support https – there have been some problems in the changeover
Mapped domains do not support https yet
-
@designsimply when I click on the link without the “s”, I go to the site but the site now has an “s” in my browser address field.
-
auxclass had the better answer! Sorry I didn’t know about the https updates before. It seems like https is the way to go. :)
May I ask why you prefer http to https? I am curious about that.
-
I have mixed passive content on my site
If we are forcing https, and if you are embedding external resources such as images using http, then I don’t think there is a way around the warnings that come from having mixed passive content on the site. The better thing to do will be to try to move the content to https if possible. If you would like help looking at a specific case, I can try to take a look if you post a URL where I can see an example of the problem in action.
I did look at https://hymnstoenjoy.wordpress.com/ just now, and I didn’t see any browser warnings on that specific home page.
-
You all be welcome –
If you think you have a problem – wait until they try and put a certificate on my mapped domain – the staff was very cautious when ask about mapped domains
good luck
-
You mention mapped domains. If I changed my site from mysite.wordpress.com to mysite.com, would that get rid of https?
Sadly yes. I have a mapped domain and there is no way I can enable https on my site even it has been suggested several times to wordpress, that this is now very important. We simply can’t buy certificates, instead they keep working on non-essential things like UI designs, editors and what not.
-
-
The fact remains that my site is still https. How do I change it to http? Would a different theme change it? (currently Splendio)
The site we are talking about is https://hymnstoenjoy.wordpress.com/How do I create a http site and ensure it stays http (not https)?
-
-
Hi everybody! Dear WP-Staff,
I’ve read the relating topics so now I feel being tricked cool. (Sorry if my English is not too perfect – I’m unfortunately Hungarian.)
It’s very OK changing the …WP.com to encrypted mode. I’m very sensitive about security and a hot protester against government surveillance as well. But!!! I think that the IT experts should carry out the modifications in a very compatible way! Now I feel a strong discrimination because more things relating to my blog don’t work after the moving from http to https (on base of investigation by Google search it could be 2014.11.24.-25.).
E.g. my embedded (flash) codes of worldtimeserver.com doesn’t work any more. My hard work on my posts is absolutely wasted time: https://evitae.wordpress.com/2014/07/06/szendvics/
The other problem is with my RSS feed on the nepszava.com (RSS-widgets ca. bottom right; and based also on WP-software!). We two (hessenwinkel and eVitea) out of 8 bloggers are discriminated by WordPress at the moment, because our RSS feeds became empty. This significantly reduces the number our visitors, so again: we work hard in vain. Now I made replace my WP feed with my e-Vitae.blogspot.com feed – temporally I hope. And I try to post parallel in my 2 blogs. It means double, great work. And u cannot imagine how many hours of my life took to look for the possible errors.
So before any type of migration it would be necessary to think about communications with other sites that don’t necessary use SSL (yet) and we are not able to force them to do so. I work in IT so I know what I’m talking about (at least I strongly believe it).
Dear Staff, could u give me a little hope?
Otherwise: Marry Christmas and Happy New Year.
Eva from Hungary :-) -
If you’re duplicating content among multiple blogs, you’re already shooting yourself in the foot. But I guess it’s your choice.
Why would your RSS feed be empty: does your blog consist ONLY of embedded material from external sources?
-
Some people want https. Others like evitae and myself like to have http only. This is so that we can have mixed content on our site eg images linked to non-secure sites. We don’t want complicated browser settings for each browser type that may access our site.
-
Dear raincoaster, “you’re already shooting yourself in the foot” – I don’t understand. Why would I do? “it’s your choice.” – no, it’s not. I strongly believe that the mistake of WordPress forces me to find some workaround. I don’t want to duplicate my posts but I need find some (perhaps temporal) solution to solve the current problem.
My RSS URL is absolutely valid: http://evitae.wordpress.com/feed/ But embedding the feet another site through an RSS-widget (in nepszava.com) it doesn’t work well because the nepszava.com (also based on WP-software) probably can’t manage the https// channel:
At the moment in the source code of the generated html page of nepszava.com (with some Hungarian text in them of course):
The good code of another RSS widget:
<h5><a class="rsswidget" href="http://kanadaihirlap.com/feed/" title="Olvasás RSS hírcsatornán keresztül"><img style="background:orange;color:white;border:none;" src="http://nepszava.com/wp-includes/images/rss.png" alt="RSS" height="14" width="14"></a> <a class="rsswidget" href="http://kanadaihirlap.com" title="">kanadaihirlap</a></h5>Our “emptied” RSS-widget code:
<h5><a class="rsswidget" href="http://hessenwinkel.wordpress.com/feed/" title="Olvasás RSS hírcsatornán keresztül"><img style="background:orange;color:white;border:none;" src="http://nepszava.com/wp-includes/images/rss.png" alt="RSS" height="14" width="14"></a> <a class="rsswidget" href="" title="">hessenwinkel</a></h5>So the href in the second a tag is generated now empty.
End all RSS-widget was correct still 24 Nov 2014 22:30:22 GMT but went wrong already on 25 Nov 2014 01:04:08 GMT – the Google search proved that.
Dear songsofhope883, these all are not about whether I like the RSS communication or not (I like it), but our visitors not necessarily can or want manage this connection type. So we need such interfaces that can continuously manage all variations of connections on both the source and the target side. This is a simple need on the web I think.
-
Sorry, previously I made a bad mistake in the last paragraph, so in correct form: “… these all are not about whether I like the RSS communication or not (I like it), …”
-
It’s not my day :-( I mean SSL not RSS in that sentence :-( What a pity that there are not preview of comments :-(
-
I’m so sorry for the trouble. As we transition to https, there are issues that will need to be worked out and clarified. What I can do to help you is go through each issue with you and try to understand it better and work with you to clearly document the problem and then report any that have a chance to be fixed on the WordPress.com side. Some things may be possible to fix and some may not.
Let’s look at the clock issue from this page first:
https://evitae.wordpress.com/2014/07/06/szendvics/For reference, here is the first embed code:
[gigya src="http://www.worldtimeserver.com/clocks/wtsclock001.swf" flashvars="color=0000FF&wtsid=US-NY" wmode="transparent" width="140px" height="140px" scrolling="no"]For that embed code to work, the clock itself would need to be able to work over https and it looks like it does not:
https://www.worldtimeserver.com/clocks/wtsclock001.swfThe gigya shortcode is not a recommended or supported embed code because the content that can be served in it varies so much, with that freedom comes security risks. WordPress.com is always working to become more secure and switching to https is a part of that.
WordPress.com supports the shortcodes mentioned in our support docs here:
http://en.support.wordpress.com/shortcodes/In this case, I believe you could get the clock to work if the clock provider was able to serve it via https as well. If not, then it will not work.
My RSS URL is absolutely valid: http://evitae.wordpress.com/feed/ But embedding the feet another site through an RSS-widget (in nepszava.com) it doesn’t work well because the nepszava.com (also based on WP-software) probably can’t manage the https// channel
I tested https://hessenwinkel.wordpress.com/feed/ using the RSS widget that comes with WordPress core on a local install of WordPress 4.0, and it worked in my test. So, whatever is causing the feed not to show for hessenwinkel at nepszava.com might be due to a setting issue in the RSS widget on that side or an issue with the widget itself (I am not sure which widget you are using or how that it is set up).
Changing to a self-hosted setup where http can still be used is a possibility for you, but I think that would take some work and you will need to switch to https eventually there anyway because more and more browsers and search engines will begin to require it or penalize sites that don’t use it in the future. If you are interested in reading more, here are some related links:
https://developer.mozilla.org/en-US/docs/Security/MixedContent
http://googlewebmastercentral.blogspot.com/2014/08/https-as-ranking-signal.htmlI have a mapped domain and there is no way I can enable https on my site even it has been suggested several times to wordpress, that this is now very important.
Enabling https for mapped domains is a planned update which is being worked on by the systems team separate from other changes happening at WordPress.com. I don’t know the timeline for when it will become available, but I do know it’s on the roadmap.
- The topic ‘How change a site https to http?’ is closed to new replies.
WordPress.com Forums 