H3S1: TCP-ports lit-rev:
<Wikipedia x Hu x Keith from WP.Buffalo-Slack x RFC-6455><a-rs><fbno>:
H4S1: Port #80:
<Wikipedia>: The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses. The port numbers in the range from 0 to 1023 (0 to 210 − 1) are the well-known ports or system ports. They are used by system processes that provide widely used types of network services.
Hypertext Transfer Protocol (HTTP) uses TCP in versions 1.x and 2. HTTP/3<RFC-9114, a-r> uses QUIC, a transport protocol on top of UDP.
H4S2: Port #443:
Hypertext Transfer Protocol Secure (HTTPS) uses TCP in versions 1.x and 2. HTTP/3 uses QUIC, a transport protocol on top of UDP. RFC.6455-1,7.8: “By default, the WebSocket Protocol uses port 80 for regular WebSocket connections and port 443 for WebSocket connections tunneled over Transport Layer Security (TLS/SSL) [RFC2818]. At the time of writing of this specification, it should be noted that connections on ports 80 and 443 have significantly different success rates, with connections on port 443 being significantly more likely to succeed, though this may change with time.”
H5S1: 443 vs 80:
Hu: Since we are working on localhost, for now, and in private web, SSL won’t be necessary<Turing>, we can stick with port-80, which is already opened, by default. According to Keith, this will also allow us to continue using fwrite, whereas we might run into issues otherwise<80%>
Hu: In our initial tests 11/4/22 flare/HTTP.client-test,int.server-2, both ports 80 and 443 worked for stream_socket_client/server. However, we have not tested HTTP requests to either port, at this time #
H3S2: Schweitzer’s opinion:
<WP.MIC-H2S77,H3S6.H4S4>In /Server/WebSocketServer.Php, Schweitzer selects 443<paraphrase><fbno>if ssl is used, and 80, if not, by defaults.
H4: Temp-close<fbno>: At this point, we have enough to move forward with port-80, so we are going to fclose this post until development on localhost is complete #
https://www.rfc-editor.org/rfc/rfc2818<2,000>, obsoleted by https://www.rfc-editor.org/rfc/rfc9110<2022>