More reliable ZMQ connection

This release addresses the issues where HARchiver would stop transmitting datapoints after a few days.

• Datapoints that can't be sent are buffered and sent on a new socket after no more than 5 seconds.
• The socket is refreshed periodically to help the load balancer.
• The executable is roughly 30% smaller because the symbols were stripped with strip -s.

Fixed compatibility issue

• Fixed a compatibility issue which would cause datapoints to sometimes be rejected by the Analytics server.
• Updated dependencies resulted in performance and stability upgrades.

Use sanitized headers

HARchiver now uses the headers sent to the upstream server in the recorded datapoint instead of the headers sent by the client.

In practice it only affects the "control" headers such as X-Forwarded-For, Mashape-*, etc.

Work better with other proxies

• HARchiver now uses the X-Forwarded-Proto header as well as the equivalent to the Mashape-Upstream-Protocol header.
• The Mashape-Upstream-Protocol has priority over X-Forwarded-Proto. X-Forwarded-Proto is used by the Amazon EC2 Load Balancers, which allows HARchiver to proxy more transparently when deployed to EC2.
• When the X-Real-Ip header is present, use it as the client IP. If not present, then use the first IP in the X-Forwarded-For header. If not present, then resort to the raw socket IP.

Public launch

First release compatible with the brand new analytics.mashape.com!

• Updated to ALF 1.0.0 format
• Renamed all special headers to Mashape-* :
  • Mashape-Service-Token to override the token that was passed (or not) on the command line.
  • Mashape-Host-Override if present, it'll replace the Host header. Useful for XmlHttpRequest in browsers.
  • Mashape-Upstream-Protocol forces the choice of protocol used to connect to the remote host.
  • Mashape-Environment sets the environment to be used in the datapoint sent to the Analytics site.
• Added the -env flag to set a default environment
• OPTIONS requests (such as CORS) do not require a Service-Token and will not be sent to Analytics unless a Service-Token was provided on the command line and/or as a header. This is necessary to make CORS possible in browsers.

v1.7.0

• Prints active settings on startup
• Improved memory usage
• Updated OpenSSL version

Fixed an issue with long running process

Fixed a broken dependency that was causing the process to become unresponsive after an hour. Only version 1.6.2 was affected.

Stability

Fixed a rare race condition that could crash the server.
Implemented a series of safeguards to prevent similar crashes from happening again.

Fixed an issue with POST data

• Fixed a case where the wrong transfer-encoding would be selected

X-Upstream-Protocol, replays

• Added support for the X-Upstream-Protocol header
• Added replays option to send base64 bodies for replays, although they aren't available in the APIAnalytics site yet
• Added library licenses and the source code in the package