Tag Info

New answers tagged

0

When you install Service SSL Certificates in WHM, you're showing the users of your server that you are who you say you are. When you use self-signed certificates, there's no authority that attests to the correctness of the certificate's information. This causes a trust warning in the browser, telling users that they may not be dealing with whom they wish. ...


0

The issue was with Jenkins itself. We originally disabled the http port for Jenkins and only allowed https. Once we allowed http again, we only allowed requests from 127.0.0.1 and that solved our issues. tl;dr: enable http port, only allow requests through 127.0.0.1


0

I think the only problem is with the proxy_pass directive. You mention http://chocolate.company.com where you should in fact use the upstream group name here. I changed the name of the upstream group to better document the change: # this is where all requests should be proxied to upstream chocolate_upstream { ip_hash; server 192.168.10.100; ...


0

My temporary "solution" is to use a short timeout on the initial calls and immediately retry if they fail. The timeout is short enough that on this server it fails and then retries again fast enough to start communicating successfully (just like when I ran it manually, cancelled it, then ran again). So far it looks like having one timeout and retry is good ...


2

I can understand not wanting to perform interdiction of HTTPS traffic, both for the UX reasons and for reducing exposure to liability for the contents of decrypted communications. Instead of having DNS resolve to your web proxy, have it resolve normally to the true address (set your DNS servers as caching, recursive resolvers). Using either WCCP or DNAT on ...


0

This should work for / (root) and all pages under / but not any subfolders. RewriteEngine on RewriteCond %{HTTP_HOST} provectium\.com [NC] RewriteCond %{HTTPS} on RewriteRule ^([^/]+)?$ http://%{HTTP_HOST}/$1 [R=301,L] If you put ^ in the second line, the rule will match only if the host is exactly provectium.com and won't match www.provectium.com.


0

You're trying to install apt-transport-https from oldstable, that depends on the old libapt-pkg4.10 instead of libapt-pkg4.12. Get the correct version. If all else fails you can find the version from stable (wheezy) here


0

I had the same issue because my default ssl was not enabled In other words: a2ensite default-ssl service apache2 restart


0

Just spoke w/ Thawte support via chat and they have confirmed it's a problem and an open case w/ Apple (since July 31, 2014) on the issue. No response / ETA on a fix as of yet.


1

Check if 443 port is open to the world or not. Trying using telnet telnet <host> 443 See if that work ? If not. Check the security settings of the load balancer instance.


0

I managed to solve my problem by adding the following lines to the .htaccess file: RewriteEngine On RewriteCond %{HTTPS} off RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}


0

If you only include the IfModule directive in a VirtualHost Directive for x.x.x.x:443, then it will only apply to that VirtualHost, and there only apply to the https protocol. 2. You could try the directive <If "%{HTTP_HOST} = 'www.dev.domain.com'"> <IfModule mod_headers.c> Header unset Strict-Transport-Security Header always set ...


2

HTTPS requests are encrypted with the server's public key that resides in the certificate. The encrypted data can only be decrypted wih the private key which only the certificate owner has access to. Even then, if you had the private key, you still have to get iptables to use it to decrypt the traffic and then inspect it. Iptables is not the right tool for ...


4

Er, that's the way it always works. If you are actually looking at a website via HTTP, you're very specifically not using HTTPS, and thus not using the certificate. You might be thinking of HTTP->HTTPS redirection; you can configure a webserver to redirect all HTTP requests automatically to HTTPS. Even though you type in HTTP, when the page finishes ...


0

Everything works fine after removing this - url.rewrite-once = ( "^/min/([a-z]=.*)" => "/min/index.php?$1", "^(.*)\.(jpg|gif|woff|tff|png|js|css|html|htm|txt)(.*)$" => "$0", "^/question2answer/(.+)$" => "/question2answer/index.php?qa-rewrite=$1", "^/$" => "/index.php" )


-1

This might not be the most elegant way, but it worked for us. Explicitly catches a regex match. (Note: maybe it should be "https://%1$1") $SERVER["socket"] == ":80" { $HTTP["host"] =~ "^(.*)$" { url.redirect = ( "^/(.*)" => "https://%1/$1" ) } }


1

Had the same problem. In my situation the following solution worked (Apache 2.2/Debian Squeeze) It seems like the ssl config was not loaded at the moment of listening. After many try and errors with the virtual host config, I added the config for SSL in apache2.conf instead of in the virtual host directive part. The ports are configured in ports.conf. After ...


0

I eventually found the solution without cancelling out the certification warnings and such. This requires the latest CURL which is 7.37.1 The right syntax is: curl --resolve yourdomain.com:443:se.rv.er.ip https://yourdomain.com


0

Have you tried using curl to connect to the IP address and overwriting the host?- curl -H 'Host: domain.com' http://10.10.10.33/


0

You don't need the hostname, you can connect by using the IP alone and pass the domain using curl. curl -k -H "Host: your-domain-name" https://ip-of-server/someURL The -k will make cURL ignore certificate errors, the -H will put the host, and curl download the result. You can pipe it over awk, grep or any other tool you have.


0

Many SSL http servers don't care what Host: header is supplied, so simply requesting https://$ipaddress/foo should work, as long as you can convince the client (e.g. wget) to ignore the certificate CN mismatch. Otherwise try something like: (echo -e 'GET /foo HTTP/1.0\r\nHost: domain.com\r\n\r'; sleep 2) | openssl s_client -connect 10.10.10.33:443 | grep ...


0

Here is the AWS documentaion for setting up HTTPS/SSL Load Balancer: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/US_SettingUpLoadBalancerHTTPS.html


-2

You can simply force redirection on default web site to - https://owa.domain.com/owa and remove "require SSL" in SSL Settings.



Top 50 recent answers are included