Future features

Any feature requests should be added to this list. The issue tracker should be used for actionable bug reports only.

New entries should be added to the list with the current date, and an explanation on what the feature should look like unless it is trivial.

Please note that we will not add features "just because." There should be a significant use case for it, and you must be able to test the feature on production traffic for us when it is done.

• Multiple frontend and backend. Only one proxy can be defined, for example :8081 to localhost:1937. For our product we need to have at least one more - 4005 to localhost:8088.(2016-10-25)
• Wishlist: Multiple backends per SNI name matched by wildcard cert. (2016-07-08, issue #86)
• Add support for external dh-params for easier rotation. (2016-03-01) (see issue #61)
• Add support for RFC5077 session tickets (2016-03-01) (see issue #16)
• Add support for OCSP stapling. (2015-07-23)
• Different backend based on NPN/ALPN headers. (2015-07-23) (issue #33)
• A fork with a different TLS library. (2015-07-23)
• Shared memory log as in Varnish. (hitchlog, hitchstat)
• Support for PROXYv2 in proxy-proxy mode (issue #11)
• Look into the logging of failed handshakes, in particular handling of older pre-SNI clients (android < 2.3, windows xp, ...) (from T275)
• Support including other files in configuration file. (from T274)
• Support for dynamic TLS record sizing to optimize performance and page load (see issue #29 and https://www.igvita.com/2013/10/24/optimizing-tls-record-size-and-buffering-latency/)
• Support for Unix domain sockets at least on the backend side (issue #257)
• Support for TLS 1.3 0-RTT, for optional faster resumption of TLS connections (2019-01-03)