Skip to content

UTF Encoding issue when multi-byte characters are present #18

Description

@lukecarroll

If a string in the JSON content contains any characters longer than one byte (ie non-ASCII), the byte array written to the stream in LongPollingTransport.GetRequestStreamCallback misses bytes due to the wrong length being passed to postStream.Write(). This results in a HTTP 400 Bad Request from the server due to malformed JSON.

I hadn't seen any activity on the project lately so I've forked CometD.NET and committed my fix - lukecarroll@2f17056

Cheers

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions