HTTP cookies are not port-specific. According to the protocol for creating and using cookies, they are associated with specific domains and paths, but not with specific ports. This means that if a server provides content on different ports, the same cookie can be used across all ports.
For example, if an HTTP response from http://example.com:8080 sets a cookie, that cookie will also be sent with all subsequent requests to http://example.com:9090 (assuming other attributes like path and domain allow it). This is particularly important when multiple applications are deployed under the same domain but on different ports, as the same set of cookies can be used to maintain user sessions or for tracking.
This behavior ensures the flexibility and maintainability of web applications, without the need to recreate and manage independent sessions or user authentication mechanisms for each port.