Don't send sentry_timestamp in the header. #28
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously
sentry_timestamp
in the header was sent in the format2019-12-13 12:02:58.94
. This suddenly stopped working on 12/12 around 16:45 CST.Sentry's documentation (see the Authentication section) says that the
sentry_timestamp
should be a UNIX timestamp. We tried sending0
and that worked just fine, but we also tried not sendingsentry_timestamp
at all and that also worked.Here is a PR removing
sentry_timestamp
from the header. What do you think?