Thanks for the update, @cpu. So it sounds like the timeline for client devs adopting POST-as-GET (PaG) support should look something like this.
- Today
- Start working on a branch of your client that transitions to PaG using Pebble as the test server
- Date X when Staging supports PaG
- Verify branch works properly against staging.
- (Optional) Release client that uses PaG only against staging.
- Date Y when Production supports PaG
- Release updated client that defaults to PaG
- November 1, 2019
- Relax because users who are up to date shouldn’t have any issues with the disabling of unauthenticated GETs
- Users who haven’t upgraded to the release from Date Y or later will break.