I'm new to SSL in IIS 6. I download and the IIS 6 Resource Kit and followed the instructions here:
http://www.somacon.com/p42.php
My IIS webpage is at: review.mprinc.com/webvts.
If I go to http://review.mprinc.com/webvts, the site is still there and if I go to https://review.mprinc.com/webvts, it appears the SSL is working.
Is that all I have to do? How do I forward the http: page to my https: one?
If SSL is working then you should redirect http to https for all site or for certain pages and a short description on how could be done can be found here How to Force Redirection From HTTP to HTTPS on IIS 6.0. Also it is recommended to configure a default page.
Related
My site was of HTTP Version and recently installed certificate. Currently it is pointing to HTTPS URL but permalinks still pointing to HTTP version of the URL. Under WordPress Settings -> General ->WordPress Address URL and Site Address URL are still pointing to HTTP version but are greyed down and I can't even edit.
How can I ensure all the permalinks are pointed to HTTPS version?
Hm, go to settings and check are the links HTTPS or HTTP. If they are HTTPS then try Really simple SSL plugin and that shoud work.
So I had github pages set up with a custom domain without problem on namecheap a day ago. Then I tried switching to Https via github's newly added support for https on pages. After too much frustration I switched over to CloudFlare for Https but I'm now getting an error ERR_TOO_MANY_REDIRECTS
Here's my DNS settings on CloudFlare.
Check your SSL setting in the Crypto tab. You should have it set to "Full". If it is set to "Flexible", then Cloudflare will use HTTP to connect to the origin, even when the client browser connects to Cloudflare over HTTPS. GitHub is probably responding with a redirect to HTTPS in this case -- not realizing that the original client is already using HTTPS, and so this redirect creates a loop.
More info here:
https://support.cloudflare.com/hc/en-us/articles/115000219871
The two typical causes of redirect loop errors are:
Cloudflare SSL options that are incompatible with your origin web
server’s configuration, and
Page Rule misconfiguration.
you can update in Custom domain github pages
https://github.com/yourusername/yourusername.github.io/settings/pages
Custom domains allow you to serve your site from a domain other than xxx.com with www, i was clear this issue with this way.
I have 2 Windows 2012r2 Servers (Dev and Production) both running IIS 8. Both were configured identically as far I as know. I am in the process of installing wildcard certs on both of them.
I installed the cert on my Dev server and it's working. One thing that surprised me though was that I didn't have to add any additional bindings to any of my site configs (eg: I didn't add https/443) and just simply changing http to https in the browser is working, and showing the cert. Why is that?
My main question though is that on my Production server, before importing the wildcard cert, I tried simply changing the url for a couple of the domains I host from http to https in a browser to see what the result would be. When I do this I'm getting a redirect loop for all https tests. ???
I don't have any https URL Rewrites configured so I don't know what the cause of the redirect loop is. It does it for all sites on this server when trying to load it using https.
example:
http://mydomain.example.com (works)
https://mydomain.example.com (redirect loop)
Safari says, "...redirected you too many times. ERR_TOO_MANY_REDIRECTS"
Chrome says, "Too many redirects occurred..."
Additionally, if I load http://localhost on the server itself it works. If I load https://localhost I get an error, "Not Found - HTTP Error 404".
I should add that this Production server is behind an F5 Load Balancer so that could be playing into this behavior as well.
The cause of the redirect loop for all sites on the Production server was an irule on the F5 LB, that shouldn't have been there, that was looping port 443 back to itself. HTTPS for all sites worked after the irule was removed.
With regards to the Dev server and https sites working without having to add a binding. I also discovered that the F5 was configured to handle certs with a wildcard cert so local certs weren't even required. The data center team didn't communicate to me that the LB was configured to handle certs for these servers.
I am using Microsoft IIS to proxy requests for WebLogic server.
I've enabled https on IIS.
[http://webserver gives error that 'page must be viewed on https' and https://webserver gives content of Default.htm file]
I've enabled https on WebLogic Server.
[http://weblogic:7001/myapp/test.jsp and https://weblogic:7002/myapp/test.jsp both works]
Communication b/w IIS and WebLogic Server is on https.
The issue is when I access application on https using webserver URL (https://webserver/myapp/test.jsp) I do get response (content of test.jsp) but when I print request.getRequestURL() in a filter, I get http URL (http://webserver/myapp/test.jsp). This is causing a issue while doing sendRedirect()...
Why are my https URLs getting converted to http? Any idea?
Thanks.
Following solved my issue:
If a plug-in is communicating to WebLogic application server then do following –
Environments > Servers > select your server > General > Advanced > check WebLogic Plug-In Enabled
Thanks again.
Newbie IIS question:
I want to setup HTTPS access for my XHTML page (not asp.net) hosted on my IIS 6.0 server. So far I have done the following:
In IIS Manager, for the particular folder, the following are set:
Require secure channel (SSL)
Require 128 bit encryption
Ignore client certificates
However when I try to access the page from IE 8.0 there is the following error:
"Internet explorer cannot display the page".
The options for using SSL and TSL are ON in the IE settings. Same error with Firefox also.
Apart from the above is there any else I should setup on the IIS server?
Have you generated a self-signed server certificate?
Here are the official instructions for setting up SSL in IIS. You can find directions here for creating a self signed certificate if that is the route you want to take.