Apache :: Allow Website To Be Accessed With Http And Https
Jun 7, 2015
I recently got a SSL-certificate for my website. Now the old links to my website (using only http) doesnt work, the visitors just getting redirected to my index page. How can I change my .htaccess so both http and https works, but keep https as the preferred? Or even better, redirect old http links to https? I'm not using www.
My current .htaccess:
RewriteCond %{HTTPS} off
RewriteRule (.*) https ://%{HTTP_HOST}%{REQUEST_URI}
I´ve read that a whole https website might be better for SEO than just a mixed version. So I want to change the whole website to https.
We are using Plesk 12 on Win 2008 R2. One Website is using DotNetNuke 7.3.2.
How can I automatically set the whole website to https?
What happens to the users that just type domainname.com without http or https.?
What is the right search engine friendly technique to permanently redirect to the https version even when the user is not using the application protocol prefix http/https?
Where can I do the setup in Plesk 12 fro Windows?
Are their any other drawbacks that I have to think over before I do the changes?
I keep hearing that redirecting from http to https is not very secure [non-SSL to SSL]. Among other reasons, one reason is that the browser may continue to think it is communicating with non secure server and may not encrypt the data. Is it true? I hope not, I am using the following -
I am trying to find out if redirecting an https URL to an http URL will still provide the security of the original https? Should the page information for the redirected http page show it as being unencrypted or shouldn't it have the same encryption as the original https?
My PHP script has an include statement. All works fine when I access the script using http. HOWEVER, when I access the exact same page using https, PHP complains that it fails to open the include file. I've checked and the include_path lists the correct dirs in both cases.
I have a custom software that runs it's own webserver. I then found instructions on how to use apache2 as a proxy that will enable ssl for that site. (long story short, my custom software doesn't support ssl and it's not an option)
i want to redirect main domain http //, www request to https://
i added this code
RewriteCond %{HTTPS} off# First rewrite to HTTPS:# Don't put www. here. If it is already there it will be included, if not# the subsequent rule will catch it.RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]# Now, rewrite any request to the wrong domain to use www.RewriteCond %{HTTP_HOST} !^www.RewriteRule ^(.*)$ https://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Recently I cross compiled Apache2.4.6 to run in my ARM cpu, and I found that http can work well if only it's own port such as 80 is listened, but if add one more port to be listened in conf file, http fails. That means http is good, but after https is on, http stop working and https is good. At the same time, I built the same apache2.4.6 in X86 gcc4.6.1, http and https can both work well. In addition, I also tried apache1.3.33 in the same ARM system, http and https can work well too. It seems like that in apache2.4.6, http can't work well if there is one more port listened in ARM system. Actually http port is listening and is established when using netstat to monitor it.
root@freescale /usr/local/apache/bin$ netstat -a Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 :::www :::* LISTEN tcp 0 0 :::443 :::* LISTEN tcp 0 0 (null):www (null):3705 ESTABLISHED tcp 0 0 (null):443 (null):3720 ESTABLISHED
I want to rewrite my all site urls from http to https and also preserve URL canonicalation like all url redirected to http://www. How to achieve this goal?
I'm currently struggling with an issue on our Apache 2.2.24 home-rolled installation on an OEL 6.2 x64 linux server that front-ends for a Glassfish cluster via proxypass.The httpd.conf manages 4 virtual hosts with each virtual host entry rewriting to HTTPS.
Anyone trying to access the HTTP address redirects to HTTPS just fine.The issue is that anyone using the HTTPS address gets redirected to the Document Root defined in Apache instead of being proxypassed to Glassfish.
I had set up a dummy DocumentRoot with a simple index.html meta redirect and what happens is that anyone directly accessing HTTPS will hit the index.html file which redirects to the the https site. At this point it simply loops to infinity.
Currently I have a URL that has HTTP. This has been given to the public. There is no doubt that they have added this URL to their favorites.
In about 2 weeks, I will be applying an SSL certificate that would add an ‘S’ to the HTTP (e.g. https)
My questions is: After applying this SSL certificate, which adds an “S”, will the link saved in my users’ favorites still work? Or do I have to add some HTML code that will redirect them?
I have installed SSL for the domain abc.com, for security reason I'd like make [url]is default for all access, that mean if the visitor type [url]on the browser, it will auto forward to[url]
I am maintaining a site that is totally on a secure folder. I have been asked to make only the things like the cart to be secure and to make the rest of the site non-secure.
there is an https and an http folder on the server all of the site is now on the https folder. I thought all I needed to do is move the pages I wanted to be non-secure to the http folder and then use an absolute address when I needed to refer betweem them.
I called my hosting people (the people who originally developer the site and made it all secure before handing to it me) and asked them about what all I need to do. they said its very complicated because I am dealing with 2 different root directories and didn't offer me much info on how to do it myself instead they just said if I can't figure it out they will do it for a price.
if there is anyway to redirect my users to https no matter what page they are on using htaccess?
I really don't fancey using full url extentions and changing them on every link on my site. I can get the homepage to redirect to https but not any other.
If there is no way to do this does anyone know the shortest hyperlink to use the redirect?
I have set up an Apache web server that has ssl enabled. If I go to https://myserver.com I get the 'it works!' page and the certificate is valid and trusted. If I go to https://myserver.com/myapp that also works (it's an Oracle weblogic deployed java app that I'm fronting with Apache).
I would like to configure Apache so that when a user goes to simply https://myserver.com it automatically directs them to https://myserver.com/myapp rather than showing the 'It works!' page. I have read some documentation and experimented with setting a redirect via the https.conf file and even the ssl.conf file but nothing seems to work. I either get a 404 or simply the 'It works! page.
We will be migrating from plesk 9 to plesk 11 and I am having some trouble finding a fix for something. Previously, http and https could either share a directory or have split directories (httpdocs and httpsdocs) for a site. Now all I see is httpdocs and I can't find a way to have separate directories.
I have a tiny "webpage" in an Apache server running on my computer. I've got for it this .htaccess file: URL...I have written it by googling,.(I don't really know very much about Apache HTTPD, but my Java suite requires this stuff, so here I am). Supposedly the first paragraph is to avoid Google Chrome from caching my files and the second part (the Order sentences) are to allow anyone to view only those kinds of files (which is otherwise let them see everything but folder roots.
And here is the httpd.conf, which I've modified almost only to change the listen port, the server name, and to replace the AllowOverride None into AllowOverride All so that .htaccess is actually used (I've deleted the comments for readability).URL....
I had never heard of something similar, "I can only load one instance of each file". In explanation, the only html file there's, runs from time to time a PHP script. Let's say I run it on localhost for example. Then everything is going fine. But I open a new tab, and load the same page (while the another one is yet open), and I'll get a 412 HTTP error. Similar thing happens if I try to load the webpage from another device. And, with my little experience with Apache HTTPD, I guess it's because of this .htaccess or httpd.conf files. Why does this happen or how can I solve it (either it be or not related to one of these files, I'll do whatever is needed)?
Apache 2.2.22 which can be found [link URL....]here[/link] in Windows 8 x86.
the hostname is www.domain.com also in the serversettings of plesk. When we go to http://www.domain.com:8443 we become redirected to https://www:8443. The only way to connect to plesk is to use https the redirect from http doesnt work.
