addon domain not working on http cloudflare - http

I've set up a parked domain and set it's nameservers to cloudflare nameservers. but I have a strange problem. I can access the parked domain only with https (e.g. https://domain.xyz).
If I access it using http it will redirect to defaultwebpage.cgi. but if I access one of the files or folders or pages (e.g. http://domain.xyz/test) the page will load without any problems. the problem only exists on the homepage (e.g. http://domain.xyz).
the cloudflare is using flexible setting.

It's not cloudflare issues, Might be there is an issues with your local end, Please try to clear your browser cache and try again. OR try to check your domain through proxy sites.

Did you create any Page Rules in Cloudflare? I understand that you use a Cloudflare Flexible SSL certificate. In order to redirect http traffic (with our without www) to https traffic you need to add a Page Rule in Cloudflare. Did you do that?
Create a page rule like this in Cloudflare:
http://*.domain.xyz/* that redirects to https://www.domain.xyz/$1

Related

Redirect Domain X to site on Domain Y, but make it look like the site is on Domain X

I'm not sure if this is possible. Not too familiar with Mod Rewrite.
I have domain1.tld registered on a hosting company and then I'm hosting a website on domain2.tld. I have forwarded domain1.tld and masked it. It works fine. Now I want domain2.tld to also show domain1.tld if I type it into the address bar.
It's running a WordPress site, so all my links are domain2.tld/link, but it only displays domain1.tld and my favicon also is gone. Is there a way I can get around this or would it be better to set up a hosting account where domain1.tld is registered, move the website there and redirect domain2.tld to domain1.tld. This would definately be the quickest and easiest way. I cannot point domain1.tld to domain2.tld or transfer it as the host does not support this TLD.
I assume your account at domain2.net does not support additional "Addon" or "Parked" domains (possible with some cPanel or maybe Plesk accounts)? I'm not sure whether a restriction on the TLD would apply here, since you're not "transferring" anything, just changing NAMESERVER or A records?
would it be better to set up a hosting account where domain1.tld is registered, move the website there and redirect domain2.tld to domain1.tld
Otherwise... Yes, that would certainly be a preferable solution.
If not, you are still going to need some kind of hosting account at domain1.tld from which you can forward requests (as a reverse proxy) to domain2.tld. Using "masked" (or "framed") forwarding is not a particularly good solution, as you have found. However, acting as a reverse proxy would require some configuration at domain1.tld, and depending on the next bit (see below) this might require more configuration.
so all my links are domain2.tld/link
If you want your site to be displayed at domain1.tld then this is something you would need to resolve. Can you make the links root-relative? Does WordPress need to know the domain/host on which it is running?
It is possible that the reverse proxy can handle this (ie. changing the link URLs in the HTML), but this requires more configuration. Or, you can roll your own proxy server.
But this all involves you having a hosting account (with some capability) anyway, so you might as well host your site there to begin with?

How can Https links from Google search be redirected to Http after the SSL was removed from site?

Recently I added SSL to my WordPress site but it started causing some problems (conflicts with Woocommerce and WP Super Cache plugins). The problem the I was having because of SSL was that the the Woocommerce cart was sometimes showing empty even after adding a product ans sometime the cart was not proceeding to checkout page. Do you think it had something to do with WP Super Cache or SSL or both? Anyway, I couldn't get it solved and removed the SSL after 2 days. But meanwhile Google had indexed the HTTPS URLs of my site and was showing them in the search results and they were returning SSL connection error. Now my question is how can I redirect all those HTTPS URLs to the HTTP ones? I asked my web host for help but said the redirection is not possible through htaccess or any other method. Was he right? How long will Google take to 'forget' these HTTPS links and show the HTTPS links again in search Results?
There are two standard ways to redirect:
At the DNS level
At the HTTP level
The DNS level can't help you because it just changes hostname. You want to keep the same hostname but change the scheme. This means you need an HTTP server to do the redirect.
In order to redirect from https to http you need to have an HTTPS service running on the computer with the IP address that the hostname resolves to.
Without that, there is nothing the receive the HTTP request over SSL and response with "Oh, this has moved to plain HTTP".
If the SSL service isn't running, then there is nothing that can do that.
(.htaccess is just a (suboptimal) means to configure an HTTP server, that does no good if you don't have the HTTP server listening on SSL).
Personally I'd fix the https issues. The world is going more https everyday so it's a backwards step to go from https to http. If you elaborate on what issues you had someone might be able to help.
However if you really want to do this then you need to run both http and https and redirect all traffic from https to http. How you do this depends on your set up (in Apache you'd do it using htaccess config).
How long it takes Google to fronded your site depends on many factors including the size and popularity of your site - which governs how often Google crawls your website. Give it a month at least for a small site. You can give it a kick by submitting your site to Google Search Console (the new name for Google Webmaster Tools).
Btw StackOverflow is primarily for programming questions so questions like this might be better asked on the http://webmasters.stackexchange.com sister site.

How can I set https: at first of my domain name

I've a wordpress site www.example.net. Usually when visitors visit my site, the domain name look like this example.net in the browser addressbar. Recently I added an SSL certificate in my website, so https://example.net/ is working well but the https: is not showing as default in my browser addressbar.
So How can I make my default domain address like this https://example.net/ , instead of example.net ?
Tell your hosting to set it up for you, and you by your own sign up in google webmaster tools, set your default domain to HTTPS instead the HTTP. That worked for me.
Also in all your internal or external links use HTTPS in the HREF or use just // instead Https://

Deploying web application: How to make just one page secure (https)

I am a new to web deployment and I am deployed a website for testing on IIS, the website is non secure (http) site but one page should be secure (https).
Can anyone suggest me how I can achieve it and it should not warn the user while switching between 'http' and 'https'.
SSL or Secure Socket Layer would be bound to a website through bindings. That is, you can tell IIS to redirect the incoming request traffics to a website, when for example the requested URL would be like http://domain.com/ or https://doamin.com, or http://200.202.150.200:8080/ or stuff like that.
Therefore, it's not a matter of IIS to set HTTPS only for one page. It's rather how to manage your URLs while redirecting user. In other words, it's a navigational matter.
I havent used IIS but I did this recently with Apache.
I did the following:
Set up a redirect for the page that you wish to secure so it redirects to HTTPS.
Set up a redirect for every other page to redirect from HTTPS to HTTP
Ensured static files such as images css and js are not affected by the above rules (These files need to work on both HTTP and HTTPS
If you need this commercially, I would recommend to use Helicon tool to redirect that particular page to HTTPS.
Using Helicon tool you can redirect the HTTP request to HTTPS for any specific page or whole site by writing the Rules.
In IIS 7 there is way to define new rules in "URL Rewrite" section for a particular web site. By this you can define a regular expiration and based on that you can redirect any pages which matches the expression to the page which you want. Lets say you are going to redirect http:\x.com\sample.aspx to https:\x.com\sample.aspx. For this do the following steps:
select your website on IIS
click URL Rewrite
Add Rule(s)
Select Blank rule
Then define your pattern in this case : lets say ^sample(any page start with sample). you can define any expression as you like.
in Action section select Redirect in Action type dropdown
in Redirect URL put https:\x.com\sample.aspx
save it and restart your website
you can then add any other rules as you want o match your request
And also in some other complex scenarios you can write your own scripts here

Need only to change links from https to http to access files with no SSL?

I have SSL enabled for subdomain.mydomain.com so I can access files via https://subdomain.mydomain.com. Now please tell me if I'm right.. if I have file somwhere in subdomain.mydomain.com called index.php I can securely access it via:
https://subdomain.mydomain.com/someFolder/index.php
but I can also access it via
http://subdomain.mydomain.com/someFolder/index.php
This time communication won't be encrypted though. So now it comes down to links only if I access files in subdomain.mydomain.com securely or not?
I will have another related question (and many more probably), but will post it as separate topic to keep things clean :)
You can force the use of the SSL site for non-https URLs. This way people cannot access the pages without encrypting the communication
In the http virtual host, VirtualHost 192.168.0.4:80, put just the line
Redirect permanent / https://subdomain.mydomain.com
That's usually how it works, but it depends on your specific webserver's setup. For example, you can configure a web server to disallow non-HTTPS traffic completely or you can even serve totally different content between HTTP and HTTPS.
Yes, using https: or http: in your URLs controls whether the access is secure or not.

Resources