-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enveloped event payloads has content-type included twice #919
Comments
@SimonWoolf can you confirm which is the correct description here? |
The second is correct for enveloped payloads. The first is for unenveloped.
|
So just to clarify, the work that needs to be done here is:
Is this correct @SimonWoolf ? |
yes |
* Removed versioning for events/functions * Fixed broken links * re-added missing sections * removed incorrect content-type entry * removed x-ably-envelope-appid from headers * removed old warning * Removed messages, presence and channel lifecycle * removed versions from partials * Added decoding sections for messages * adressed message comments * Added presence decoding sections Co-authored-by: Mark Woulfe <[email protected]>
Issue raised by Paul:
the enveloped event payloads have content-type listed twice https://www.ably.io/documentation/general/events#envelope-examples and I think the second one is correct.
The text was updated successfully, but these errors were encountered: