How do you encrypt traffic to a server that can't do HTTPS?
An older web server on a screened subnet is serving unencrypted web traffic. The server is not capable of serving HTTPS traffic directly, but the firewall is capable of doing so. Which of the following should be done to encrypt all traffic coming into the web server from outside the network? (Choose two.)
Community Votes
100% of anonymous learners picked answer DE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests SSL/TLS offloading; the trap is assuming the certificate must be installed on the web server or that port 80 traffic should be forwarded to port 443 on the server, but the firewall must terminate TLS because the server lacks HTTPS capability.
When a legacy web server cannot handle HTTPS, CompTIA Network+ N10-008 community consensus is to perform SSL/TLS termination at the firewall: install the certificate on the firewall and forward incoming HTTPS (port 443) to the server's HTTP port 80. This encrypts all external traffic while the server continues receiving unencrypted traffic internally.
Option B (forwarding port 80 to port 443 on the server) is a common wrong answer because it appears to redirect HTTP to HTTPS, but it requires the server to handle HTTPS, which the question explicitly says it cannot. The correct pair is D and E, not B/E or A/B.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
- The server is not capable of serving HTTPS directly, so security must be handled at the firewall. Installing a certificate on the firewall (E) lets the firewall terminate TLS and decrypt traffic.
- Incoming port 443 traffic from outside should be forwarded to port 80 on the server (D). This way, external clients connect over HTTPS to the firewall, and the firewall forwards decrypted HTTP to the server. This is the standard SSL/TLS termination or offloading model.
- The highest-voted comment [1] correctly states: "Install a certificate on the firewall: The firewall should be configured to handle the encryption and decryption of HTTPS traffic. Incoming port 443 traffic at the firewall should be forwarded to port 80 on the server."
Why the Other Options Are Wrong
- Option A is wrong because installing a certificate on the server does not help if the server cannot serve HTTPS traffic; the server has no TLS stack or listener to use it.
- Option B is wrong because forwarding port 80 to port 443 on the server would require the server to listen on 443 and handle TLS, which contradicts the stated limitation.
- Option C simply forwards port 80 to port 80, keeping HTTP unencrypted and providing no encryption or redirection to HTTPS.
- Be careful not to choose B/E or A/B. B is a common mistake that assumes the server can handle HTTPS after the firewall forwards traffic, but the whole point is that the firewall must terminate SSL.
Community Comment Notes
- The community overwhelmingly voted for D and E with 73 votes. Comment [3] highlights the key phrase: "The server is not capable of serving HTTPS traffic directly (no port 443 on Server)." This directly points to D/E.
- Comment [2] notes that web users should not be expected to connect over unencrypted internet connections, reinforcing the need to terminate HTTPS at the firewall.
- One comment [4] incorrectly suggested A and B, showing a common misunderstanding of SSL termination. The correct answer is D and E, not A and B.
Official Reference
Exam Strategy
Look for phrases like 'server is not capable' and 'firewall is capable' — these indicate SSL/TLS termination at the firewall. When that appears, the answer always involves installing the certificate on the firewall and forwarding the secure external port (443) to the internal unencrypted port (80).