A client sends a request to a web server's conventional Hypertext Transfer Protocol Secure (HTTPS) service port, and the server later replies. Explain how the service port is represented as a destination port in the request and as a source port in the reply. State the port number given in the refresher.

### Why this is right The service port changes its source or destination role with packet direction. A request travels toward the server, making the server's HTTPS service port the destination; the reply travels from that server service, making the same port the source. ### The concept The refresher gives TCP port 443 for HTTPS. A port is a field in the TCP or UDP header that helps the receiving device map traffic to an application. This mapping explains why the same service port can be a destination in one direction and a source in the reverse direction. Port numbers are conventions, not a guarantee that traffic is truly the named application; the material notes that modern hardware firewalls can detect traffic sent on an unexpected port. ### What a good answer covers - HTTPS is associated with TCP port 443 in the refresher. - Port 443 is the destination port in the client request to the web server. - Port 443 is the source port in the server reply. - Port numbers help map traffic to applications but do not prove the traffic's content. ### Terms - **HTTPS**: Hypertext Transfer Protocol Secure. Encrypted web traffic. - **TCP**: Transmission Control Protocol. A transport protocol that supports reliable delivery. - **Port**: A transport-header number used to direct traffic to an application. - **Destination port**: The port associated with the receiving application in a packet. - **Source port**: The port associated with the sending application in a packet. - **Transport header**: Packet information that includes source and destination ports. ### Remember The packet's direction determines whether the server's service port is the source or destination.