0004873: WebSocketReader is using ISO-8859-1 instead of UTF-8 via the ReadStream

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0004873

[Resin]

block

always

11-24-11 05:45

11-28-11 12:01

Reporter

ihristov

View Status

public

Assigned To

ferg

Priority

normal

Resolution

no change required

Status

closed

Product Version

4.0.24

Summary

0004873: WebSocketReader is using ISO-8859-1 instead of UTF-8 via the ReadStream

Description

As discussed in the 0004818 issue, the data transfer over WebSocket is done using UTF-8, and currently the _readEncodingName="ISO-8859-1" in the ReadStream.

Additional Information

Most of the information is already provided in the 0004818 issue. For more information don't hesitate to ask.

Attached Files

Relationships

Notes
(0005633) ferg 11-28-11 12:01	The encoding in the ReadStream is irrelevant, because only the binary (8-bit byte) data is read from it. For a bug report like this, it's more helpful to give the actual error that's occurring. Internal values aren't themselves bugs. If they're mentioned at all, it should be in a note to the actual bug report not the bug itself.

Issue History
Date Modified	Username	Field	Change
11-24-11 05:45	ihristov	New Issue
11-24-11 05:45	ihristov	Issue Monitored: ihristov
11-28-11 12:01	ferg	Note Added: 0005633
11-28-11 12:01	ferg	Assigned To	=> ferg
11-28-11 12:01	ferg	Status	new => assigned
11-28-11 12:01	ferg	Status	assigned => closed
11-28-11 12:01	ferg	Resolution	open => no change required
11-28-11 12:01	ferg	Fixed in Version	=> 4.0.25

Mantis 1.0.0rc3[^]

30 total queries executed.
26 unique queries executed.