1.14.0

Chore

• tag 1.14.0 release (e4e9d089)
• add slack travis output (aa662661)

Bug Fixes

• limit valid months to acceptable range (a06c5ad6, closes #350)
• enforce fail.value.message to string (c3b39161)
• fix dockerfile for automated builds (b4f1dcef, closes #414)
• Allow arbitrary args for options and head functions (46d2c1dc)
• decode and process crypto-key header correctly (f546ed78, closes #410)

Features

• allow logging to batch send to aws firehose (cad54238, closes #421)
• update logging for newstyle twisted and file output (547eb1ed, closes #419)
• bump autobahn/twisted reqs to 0.13/16.0 for utf8 fix (89dc0c28, closes #351)

1.13.2

Features

• validate v0 tokens more thoroughly (77373cd6, closes #406)

Bug Fixes

• Clear corrupted router records (5580e0d2, closes #400)
• clear only the node_id in the router record (a1ee817c, closes #401)

1.13.1

Test

• fix timing issue in last connect test (c4039df1)

Chore

• fix changelog and clog for past commit oopsies (90c3ab16)
• update version for 1.13.1 (7a960b4c)

Bug Fixes

• default api_ver to v0 for message endpoint (86ba66d4, closes #395)

1.13

Features

• accept nack messages, log code for ack/unreg/nack (2030a4df, closes #380)

Bug Fixes

• send raven calls to event loop (d35a78d4, closes #387)
• capture ValueError for empty notifications arrays (ce27f1e3, closes #385)
• don't return 503 for disconnected user (43a2e906, closes #378)
• force header values to lowercase underscored values (b4517aeb, closes #373)
• change message_type to message_source (d603902c)
• pass TTL Header value to GCM (c5ae841c)

1.12.1

Bug Fixes

• Normalize encryption headers. (b9c3cc57)
• allow stored ttl of None to be treated as 0 (2b75be5f, closes #366)
• silence missing TTL errors from sentry log (c167ee2f)

1.12.0

Doc

• add text and links for 400:111 errors (515be293)
• update CONTRIBUTING.md doc to match our style (214e8a77)

Features

• upgrade autobahn/twisted to 0.12/15.5 (47597a0d, closes #180)
• add user-agent logging to acks (1dbe3460)

Bug Fixes

• allow webpush w/no ttl & cleanup 400 logging (1f01cd70, closes #358)

Chore

• bring project up to standard guidelines (c2baf49f, closes #344)

1.11.0

Features

• Log notifications out of autopush nodes for data on when they were
  actually delivered to clients. Issue #331.
• Added VAPID auth support to incoming Push POSTs. Issue #325.
  This does not yet use token caches since that will introduce database
  changes as well as impact a fair bit more code.
• Require TTL header for all incoming subscription updates. Issue #329.
• Added "Location" header to all successful outbound webpush subscription
  update responses. Issue #338.
• Whitelist the "Authorization" header for CORS requests. PR #341.
• Add a "WWW-Authenticate" header for 401 responses. PR #341.

Bug Fixes

• Use appropriate 400, 404, 410 status codes for differing message endpoint
  results, rather than always a 404. Issue #312.
• Do not send useless 'ver' across GCM bridge. Issue #323.

Backwards Incompatibilities

• The TTL header is now required for all subscription updates. Messages without
  this header will return a 400 error (errno 111).

1.10.0

Features

• Tag logged notifications based on whether they're for a webpush user or not.
  Issue #315.
• Add maintenance.py script for use in AWS Lambda. Issue #254.
• Add use_webpush base tag for websocket connections using web_push.
  Issue #205.
• Add log message if routing connection is refused. Issue #283.

Bug Fixes

• Increase the type of connection loss exceptions caught by autopush that
  occur during deploys and node losses. Issue #306.

1.9.0

Features

• Utilize router last_connect index to track whether a user has connected in
  the current month. Issue #253.
• Add message table rotation for webpush users. Issue #191.
• Capture Authorization header for endpoint requests for logging. Issue #232.
• New Bridge HTTP API. Issues #238, #250, #251
  In cooperation with the GCM client work the HTTP Bridge API has been
  simplified. The new method has been detailed in /api/endpoint.py.
  In essence: The API is now bearer token based, and uses the form
  /v1/{BridgeType}/{BridgeToken}/registration[/{uaid}/[subscription/[{chid}]]]
• Tag endpoint requests with a unique ID. Issue #268.
• Fixed document reference to HTTP API to be a deep link.
• Pass either Encryption-Key or Crypto-Key per WebPush spec change. Issue #258
• Removed refences to obsolete simplepush_test package.
• Convert outbound GCM data to base64. This should resolve potential
  transcription issues with binary encoded data going over the bridge.
  Issue #289
• Record Requesting Hostname to metrics. Issue #228
• Add key hash for UAIDs NOTE: enabling this will break all currently stored
  UAID records.

Bug Fixes

• Fix bug in GCM router call not getting appropriate params dict. Issue #271.
• Ensure rotating message table exists on startup. Issue #266.
• Fix Running documents to reflect usage of local DynamoDB JAR server. Issue
  #265.
• Fixed scope issue around the Bridge API delete functions.
• Fix db test bug with month addition to properly handle December. Issue #261.
• Relax endpoint TLS cert requirement for https scheme. Issue #249.
• Add endpoint names to the docs. Issue #223.
• Moved Obsolete command arguments out of required path, and allow tester to ignore local configuration files. Issue #246

WebPush

Configuration Changes

• It is recommended that the following config options be moved to
  .autopush_shared.ini
  --gcm_enabled
  --senderid_list
  --senderid_expry

Backwards Incompatibilities

• The previous Bridge HTTP API has been removed.
• The Push message update mechanism has been removed. Issue #279.

Deprecated

• The following configuration options have been deprecated and will soon
  be removed:
  --log_level
  --external_router (replaced by --apns_enabled)
  --max_message_size

Update for 1.8.1

_Configuration Update Note:_

please include in
.autopush_endpoint

auth_key=[key]

Where key is a value generated from bin/autokey

This value is used to derive the bearer token value.