Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What are the requirements to implement the HTTPS protocol? I know that I need an HTTPS server that contains a certificate. Please guide me to implement HTTPS.

share|improve this question

migrated from Jun 3 '10 at 20:41

This question came from our site for professional and enthusiast programmers.

Are you trying to stand up a HTTPS server, or are you trying to actually write one? – Joe Jun 3 '10 at 15:17
im trying to stand up a https server – simplyblue Jun 3 '10 at 15:20
Did you try Googling "HTTPS HowTo [Name of the Server Software you're using]". If not, start there, and ask more specific questions here. – Chris S Jun 25 '11 at 14:12

Depends on the web server. Typically, you need:

  • Port 443 (or whatever port you're using) open on the virtual site (for Apache that's the Listen directive in the VirtualHost section of your config file, in IIS you have to add a host header)
  • A valid security certificate
  • A credible issuing authority if you're using this for a public website and don't want a security warning from the browser (something like Verisign, Thawte, RapidSSL, etc.)
  • A unique IP address (or rather, the IP/port combination you're using has to end up serving the website)
  • The firewall port open for 443 (or whatever port you're using)
share|improve this answer

You can configure a HTTP Server like Apache to provide HTTPS by installing mod_ssl and configuring it with a certificate, etc. in /etc/httpd/conf.d/ssl.conf (Red Hat / CentOS).

Or you can use a software reverse proxy / SSL Offloader like nginx to provide SSL termination to your HTTP Server. In this case the certificate resides on the proxy and does the SSL negotiation, etc. and proxy_pass[es] the traffic to the HTTP Server.

Or you can use a hardware reverse proxy / SSL Offloader like F5's BIG-IP which is just a dedicated device that does local traffic management in addition to SSL termination. Same as nginx, certificate resides on the device and passes the traffic to the HTTP Server.


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.