c560b9229c
Update to the latest version of the abusive message filter
2022-03-01 10:43:12 -08:00
935e268dec
Parameterize sitekey
2022-03-01 10:40:42 -08:00
3a1c716c73
Remove an unused rate limiter
2022-02-25 13:50:17 -08:00
f3457502a6
Support different v2 captcha actions
2022-02-25 13:49:47 -08:00
7ded802df4
Update to the latest version of the abusive message filter
2022-02-24 17:30:02 -06:00
d3cd1d1b15
Use GetLatestConfiguration in config manager
...
Use StartConfigurationSession/GetLatestConfiguration instead of
GetConfiguration since the latter has been deprecated
2022-02-23 15:36:33 -06:00
f5a75c6319
Simplify RateLimitExceeded with no retry-duration
...
- Avoid passing negative durations in error cases
- Drop unused message
- Return a duration for a bad forwarded-for
2022-02-23 15:25:24 -06:00
ae3a5c5f5e
Return a Retry-After on rate-limited responses
...
Previously, only endpoints throwing a RetryLaterException would include
a Retry-After header in the 413 response. Now, by default, all
RateLimitExceededExceptions will be marshalled into a 413 with a
Retry-After included if possible.
2022-02-23 15:25:24 -06:00
43792e2426
Update to the latest version of the abusive message filter
2022-02-22 11:03:41 -05:00
551d639951
Update Postgres driver to 42.3.3
2022-02-18 10:41:29 -05:00
c367a71223
APNS: include a collapse-id for non-VOIP notifications
...
This has two benefits:
- The APNS server should only send an iOS client a single push
notification for any missed messages while the device is offline
(server-side coalescing). Note that the client can still turn that
into multiple "user notifications" as it pulls from its queue.
- If multiple notifications get delivered but iOS is unable to process
them (say, because the phone just restarted and hasn't been unlocked
yet), the user should only get one "You may have received messages"
notification (client-side coalescing).
2022-02-18 10:41:10 -05:00
d259ef0348
Update rate limit exceeded counter
2022-02-17 13:23:48 -08:00
288cbf4a80
Clean up null-ability of incoming message entity fields
2022-02-17 13:23:48 -08:00
ba5e5a780f
Throw an exception instead of using Optional<Resposne>
2022-02-17 13:23:48 -08:00
73fa3c3fe4
Add test for content length validation
2022-02-17 13:23:48 -08:00
579eb85175
Reject invalid envelope types
2022-02-17 13:23:48 -08:00
b2b20072ae
Add `MicrometerRegistryManager`
2022-02-17 13:18:30 -08:00
a2c4d3fe95
Use a strong reference to the application shutdown gauge
2022-02-17 13:18:30 -08:00
31e2be2e4d
Fixup invalid accept-language counter
...
- Fix name
- Add platform/version tags to the counter
2022-02-10 11:57:25 -06:00
9f5d97e1c6
Silence noisy warnings for invalid Accept-Language
2022-02-10 11:57:25 -06:00
baaae6cd9f
Add `@NotNull` to controller args where appropriate
...
Notably, `@Valid` doesn't imply `@NotNull`
2022-02-10 11:57:04 -06:00
ed398aa7b9
Add `DeviceCapabilities.pni`
2022-02-09 15:56:01 -08:00
6e2ae42dab
Add platform to metrics
2022-02-09 15:55:07 -08:00
7f832ad783
Update to AWS SDK 2.17.125, 1.12.154
2022-02-07 16:46:25 -08:00
2ce6f8cb6c
Update to Dropwizard 2.0.28
2022-02-07 16:46:18 -08:00
2574125199
Update libphonenumber to 8.12.42
2022-02-07 16:45:48 -08:00
41bf2b2c42
Add a binary format for incoming messages
...
The existing, general incoming message endpoint accepts messages as
JSON strings containing base64 data, along with all the metadata as
other JSON keys. That's not very efficient, and we don't make use of
that full generality anyway. This commit introduces a new binary
format that supports everything we're using from the old format (with
the help of some query parameters like multi-recipient messages).
2022-02-07 16:05:03 -08:00
51bac394ec
Update to the latest version of the abusive message filter
2022-02-02 17:32:45 -05:00
b696649c9d
Update to the latest version of the abusive message filter
2022-01-31 16:24:09 -05:00
b4828ad8de
Update embedded-redis to 0.8.2
2022-01-31 13:01:52 -08:00
639d634426
Restore displaced UUID from deleted accounts table when present
2022-01-31 13:01:36 -08:00
5358fc4f43
Use `setRegistrationLockFromAttributes`
2022-01-31 12:56:59 -08:00
6a654ab90b
Update to the latest version of the abusive message filter
2022-01-28 11:26:40 -05:00
99eda80a78
Measure rate limit challenge responses by platform
2022-01-27 16:05:52 -05:00
a6182acc9c
Require any transitive dependencies on log4j to use 2.17.1
2022-01-27 10:25:13 -08:00
2241e4d8ea
Update to the latest version of the abusive message filter
2022-01-26 16:30:45 -05:00
cbbdea1ba4
Impose more stringent requirements on cardinality checks
2022-01-26 16:13:12 -05:00
05e7c98620
Return an `AccountIdentityResponse` when changing phone numbers
2022-01-26 14:44:53 -05:00
1f1d618dea
Rename `AccountCreationResult` to `AccountIdentityResponse` (since it's not just for account creation any more)
2022-01-26 14:44:53 -05:00
b18117ef89
Add tests for unidentified access when requesting profiles
2022-01-25 14:07:44 -05:00
44cb796574
Add more detail to "could not get acceptable languages" logging
2022-01-25 12:21:35 -05:00
ccf60ffc4b
Update to the latest version of the abusive message filter
2022-01-25 10:39:50 -05:00
f69db11f42
Drop some unused dynamic configuration properties
2022-01-21 18:46:37 -05:00
96a680dcf0
Remove displaced account from directory when changing numbers
2022-01-21 18:46:11 -05:00
c8367c9b7a
Update to the latest version of the abusive message filter
2022-01-14 14:48:08 -05:00
c612663490
Handle `null` `AccountAttributes` when verifying linked devices
2022-01-14 14:47:46 -05:00
de5d967d18
Track metrics for dynamic config load failures
2022-01-14 14:47:12 -05:00
7fc63f7847
Allow callers to specify one or more dynamic config classes
2022-01-14 14:45:29 -05:00
49009cbcad
Apply GitHub stale application
2022-01-07 11:37:52 -06:00
b5fbeffb86
Remove obsolete deployment files
2022-01-06 12:52:37 -08:00
Chris Eager