Optimizer 2.9.4

29 October 2020

Bug Fixes

  • We fixed a bug where we were mistakenly blocking OPTIONS requests in certain scenarios

Optimizer 2.9.3

6 October 2020

What’s New

  • When the X-Forwarded-For header contains multiple IP addresses, we are now logging only the first IP address for delivery records.
  • For added protection, we now log an empty value if a request’s peer IP address is not a valid IP4 address.
  • We increased reliability of our server cluster when it receives a request to rotate logs.
  • In order to improve security, we tightened up our handling of device_id in logging

Bug Fixes

  • We fixed a bug where we were mishandling names of SIM providers that contain linefeed characters.
  • We fixed an issue where we weren’t logging app IDs to certain delivery records.

Optimizer 2.8.0

16 July 2020

Bug Fixes

  • Previously, when a customer server shut down an established connection, we returned a 500 ECONNRESET error. We’ve now fixed the issue by resending the request.
  • We fixed a bug where we were rejecting a request and returning the Exit Warning page if we saw a 30x Redirect that was a relative path.
  • We updated our optimizer to meet current standards of accepting URLs that don’t have paths before query strings.

Optimizer 2.7.3

24 June 2020

What’s New

  • We’ve re-coded timeouts to ensure that websockets gracefully get upgraded from the default timeout to 30 seconds. This will result in more reliable handoffs for websocket requests.
  • Delivery record metadata is now more consistent across products.
  • Functionality has been added to support HTTPS proxied requests between MAX / WRAP / SWITCH SDK apps and the optimizer. New client SDK code will take advantage of this new functionality.
  • Response messaging is now more explicit when access is refused by the whitelist.
  • Code enhancements have been completed in preparation for more efficient log processing.
  • To improve our troubleshooting ability on REACH, we have increased the amount of metadata logged when 403 is returned by the optimizer.

Bug Fixes

  • We fixed misleading log messaging claiming that a whitelist was missing when it wasn’t.
  • We squashed a bug where data used by ads served in a MAX or WRAP app wasn’t being logged against the app.
  • In cases where we are using X-Forwarded-For (XFF) header, we are now checking that it is a valid IP. If it’s not, we use the peer’s IP.
  • Our shortcode service was appending a forward slash, which would return 500 in some instances. It’s now fixed.