Tag Info

New answers tagged

0

The answer to this was using EWS. There is an application called DavMail which functions as an Exchange gateway. This was simple to set up, runs as a service and solved my problem. This tutorial was very helpful.


1

Even tough HTTPS traffic cannot be proxied in a strict sense ('cause, otherwise, the proxy software will act as a "man in the middle", that is exactly one of the reason SSL has been developed for, to avoid), it's important to remark that common software proxies (like SQUID), can correctly handle HTTPS connections. This is possible thanks to the HTTP CONNECT ...


4

Yes, HTTPs will put a damper on network caching. Specifically because caching HTTPs requires doing a man in the middle type attack - replacing the SSL certificate with that of the cache server. That certificate will have to be generated on the fly and signed by a local authority. In a corporate environment you can make all PCs trust your cache server ...


0

Turns out I needed create a new security group with HTTPS enabled, then add that to my instance. I can provide more details if anyone is interested.


3

It appears you're using GoDaddy to redirect https://sendsonar.com/ to the Heroku-hosted www subdomain. GoDaddy's DNS manager's redirects don't support HTTPS (as GoDaddy's redirect services servers don't have your SSL certificate installed).


3

You should use a different server block for each "type" of domain you manage, so that you don't have to use if statements to test the $host variable. # Domains to serve only via HTTPS server { server_name domaintoredirect1.tld domaintoredirect2; listen 80; return 302 https://$host$request_uri; } server { server_name domaintoredirect1.tld ...


0

Any attempt at creating an if statement to return the https version of the site will result in a redirect loop (as your condition, server_name is not changing after the redirect, so will always match the condition and redirect again...). With that said, what I would recommend would be to set up individual configuration files per virtual host/subdomain (I ...


2

What is you'ur threat model? What are you protecting against? What, for that matter, are you protecting? We cannot make that business decision on your behalf, nor would you want us to do so. You own the resources (transmission, processing, data, and the costs thereof), and so you must determine what risks you will accept.


0

Not an issue with CloudFlare at all because we're not running on the domain in any way (it looks like you may be trying to activate through a hosting partner).


0

ncat --ssl from nmap worked well for me: printf 'GET / HTTP/1.1\r\nHost: github.com\r\n\r\n' | ncat --ssl github.com 443


2

I found a way to turn off HSTS from an answer on a Wordpress support forum of all of places: https://wordpress.org/support/topic/want-to-turn-off-http-strict-transport-security-hsts-header#post-6068192 You can send back a header that will turn off HSTS caching. Tested in Chrome with this example before_filter in a Rails 4 app: ...


-4

Yep it is possible. Here is a good tutorial. But another, simpler way of doing this would be with a .htaccess file.


0

Are you sure rpc over https is the only literal option? Any chance they have EWS or OWA available? I'm not aware of an RPC-based linux client; even the Mac Outlook client from Microsoft uses EWS, not RPC over https.


3

You will need to add the intermediate certificate into the IIS SSL configuration. For details see: https://support.godaddy.com/help/article/4875/installing-an-ssl-certificate-in-microsoft-iis-5-6 You can test if the intermediate certificate is provided by IIS with: echo ""| openssl s_client -showcerts -connect tours.vht.com:443 The intermediate certificate ...


11

You're most likely missing the intermediate GoDaddy certificates on your server. Most desktop browsers cache these, but I don't think mobile ones do. Check the GoDaddy Article on intermediate certificates with full instructions on acquiring and installing the ones from them. Generally, certificates come as a "chain". The top Certificate Authority does not ...


0

Yes there is a way to do https WCCP redirection without MITM. You have to force Squid not to ssl-bump incoming SSL traffic. ssl_bump none all HOpe that helps. I have a complete article here that goes into WCCP redirection using a Cisco ASA including both http and https. Web SSL Proxy redirection using WCCP Ccisco ASA and Squid 3.4+


-1

Okay, this is some kind of embarrassing. I forgot to run a2enmod ssl.


1

That's the expected behaviour. You are using vhosts on a single IP address where you both listen on HTTP and HTTPs. So the server block handling SSL is acting as the default one for everything going to this IP port 443. You won't be able to refuse the SSL handshake but after it has been completed you can forbid further HTTP requests not targetting a ...


0

This is resolved. I stuck to my original nginx config and used a CloudFlare page rule to force HTTPS. The rule used was: http://*gistbook.io/* => always use HTTPS



Top 50 recent answers are included