[feat] Validate proxies list before protocol decoder

[getlarge]

Would you mind removing this todo and opening an issue instead?

Originally posted by @mcollina in moscajs/aedes#334

[robertsLando]

@getlarge Would you mind to submit a PR for this?

[getlarge]

Yes i might make a proposal next week.
By the way, there is still an issue in the with the protocol decoder when Aedes broker is used behind a TCP proxy which handles SSL termination.
The packet is splitted in two, on one side the protocol proxy header and the TCP buffer on the other.
Any help to solve this would be appreciated.

[robertsLando]

Would you mind to open a new issue about that? Just to keep track of it. Maybe @mcollina could help to point us in the right direction to fix this Daniel

…

On 23 Jan 2020, at 20:39, getlarge ***@***.***> wrote:  Yes i might make a proposal next week. By the way, there is still an issue in the with the protocol decoder when Aedes broker is used behind a TCP proxy which handles SSL termination. The packet is splitted in two, on one side the protocol proxy header and the TCP buffer on the other. Any help to solve this would be appreciated. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[robertsLando]

@getlarge should this be moved to aedes-server-factory or protocol decoder libs instead?

[getlarge]

Good question, protocol-decoder might be a better place. We could still reuse that logic inside the server-factory via an option that could be overridden by user like protocolDecoder, serverFactory.

[robertsLando]

Moved to protocol decoder