DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43678>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43678 Summary: Handle META tag http-equiv charset? Product: JMeter Version: 2.3 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: HTTP AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] The HTML tag: <META http-equiv="Content-Type" content="text/html; charset=utf-8"> is treated by browsers the same as the Content-Type header. At present (JMeter 2.3) JMeter does not extract this information, it only uses headers. If no charset is present, then the platform default encoding (overridable by defining sampleresult.default.encoding) is applied when converting the response to a string. This means that the conversion of the responseData to a string may not produce the correct result - for example in the Tree View Listener, and presumably in Post-Processors. JMeter could extract the content-type from the data. It probably needs to check that the data is intended to be used as HTML first - i.e. the existing Content-Type should specify text/html. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
