SecureSocket | TCP Unix socket with SSL support | TCP library

Use the HttpClient to establish the initial http(s) connection and then detach the socket. Here's an example with http. You should be able to adapt to https. Note how the initial connection is made over http, but upgraded by adding the appropriate request headers. (You'll need to adapt the headers to the security scheme required by your websocket server.)

Here is how you can pass an endpoint as a parameter to a function.

The error was my own wrongdoing in a redux middleware.

I used forEach on an object in the middleware, where I would then call return next(action) if the parameters were not met for the middleware, which would effectively create a new action being called on each forEach recursion.

Thank you to everyone who contributed an answer.

Flex Builder 3 supports Flash Player version 10 here and SecureSocket will be available Flash Player version 11 or Higher here.

Historically unencrypted application protocols were usually assigned their own port (e.g. 80 for http, 25 for smtp).

ALPN: Nowadays most traffic is encrypted via TLS which is a secure transport protocol. Any application protocol can use it. Instead of using new port numbers for application protocols a different solution is available: TLS supports an extension known as ALPN (Application-Level Protocol Negotiation) which allows client/server to tell the peer which protocols they support and what they prefer (possibly with a fallback to a protocol deduced by the port number -- which is great for backwards compatibility)

(Side note: There was also a precursor TLS extension known as NPN "Next Protocol Negotiation" serving a similar purpose, but it is deprecated for various reasons)

Most common use case is http/2: Servers listen on port 443 and offer to speak http/1.1, http/2 and let's say spdy. The browser will make a TCP connection to server port 443 and let's the server know which protocols it supports. The server will then choose which protocol to speak (based on the list the client sent and what the server application supports). For backwards compatibility, client/browsers will fallback to http/1.1 if no protocol was negotiated.

Negogiation & Priority There are 3 cases:

• Client or Server does not support the ALPN extension: No protocol was negogiated

• Client and Server support ALPN but have no common protocol: No protocol was neogogated

• Client and Server support ALPN and there is one or more protocols both support: The protocol with highest priority is taken.

Dart support: Dart added support for ALPN some time ago and exposes it via the optional named supportedProtocols parameter to

• SecureSocket.conect for the client part
• SecureServer.bind for the server part

Once a TLS connection has been established, both ends will be able to see the negogiated protocol via SecureSocket.selectedProtocol. If the peer does not support the ALPN TLS extension or there was no common protocol, then selectedProtocol will be null.

The protocols in supportedProtocols are specified in decreasing preference (the first one in the list which is common between server/client will be chosen).

ALPN identifiers There are no real restrictions on what the protocol identifiers can be. Your application can use its own. Though for public protocols, usually RFCs will recommend which identifiers to use, for example RFC 7540 specifies in section 3.1:

"The string "h2" identifies the protocol where HTTP/2 uses Transport Layer Security (TLS)"

Inspect it yourself: If you are very curious you can use a network packet inspector, like newer versions of wireshark, to inspect TLS traffic and see what ALPN protocols are offered.

Flash CS6 > menu File > Publish Settings.

At the top right corner there's a Target dropdown list. You should pick an option with AIR int it, otherwise AIR classes won't be available and Flash won't compile the code that uses AIR classes.

Then, you are to import classes, not packages: