Hot answers tagged https
It's easier to maintain if you have one certificate, and there are no real downsides. You can put as many unrelated domains as you like on a certificate, so putting the www subdomain on seems fairly reasonable. Just use one certificate IMHO.
Do you have routing and remote access service installed? If yes, try to disable it (RRAS uses SSTP by default and it listens for 443 port and lsas.exe process which is using port in your situation is used for IPSEC also).
but all the ones I found describe the creation of a certificate pair to decrypt/re-encrypt the traffic - something I do not want to do. What you are asking for simply isn't possible because of how the https protocol works. Your options are: Permit outgoing https through your firewall, and don't attempt to use any proxies Configure clients to use your ...
Try hitting your site with the SSL Server checker on ssllabs.com. It looks like something about some SSL clients is causing them to abort the handshake. This could be various scanners, or it could be some clients are rejecting something about your SSL connection and are dropping it. Many clients will retry with a downgraded connection which is why the ...
Try this RewriteRule ^/protected-page/(.*) https://example.com/protected-page/$1 [R,L] reference : http://httpd.apache.org/docs/current/rewrite/intro.html
It turns out that it was simply an error in the web.config file. These two answers on SO were the solution: http://stackoverflow.com/a/26581326/1286358 And the reverse http://stackoverflow.com/a/26539003/1286358 Strange that it was working on both http and https once and then just stopped.... there must have been some other configuration changes ...
I think you're going to run into major issues running both IIS and VisualSVN, which installs and runs on Apache, on the exact same server. If I were you, I'd separate them out and give each web server their own VM. I know this doesn't directly answer your question but I'm wondering if your original posted problem is not a symptom of trying to run both web ...
I know it is a old question but i had the same problem and solved using this in squid.conf dns_v4_first on Regards
For an Ubuntu server (assuming you installed with apt-get install jenkins): You'll want to edit /etc/default/jenkins at the bottom of the file, edit Jenkins_args. In my args, I've disabled http access (using -1) and put SSL on the default Jenkins port (8080). The most important part here is that you sent an httpsPort and certificate/key (if you have one, ...
Only top voted, non community-wiki answers of a minimum length are eligible