1. Each content byte is stored as 2 bytes in StringBuffer.
2. To convert html/text to Java String it should consider the charset meta tag
This causes problems where the body is an octect stream. If you wish to output the messages to a file and then extract the octect streams (which I do) some bytes are not correctly exported as a default character set is persumed.
Any easy way around this to export just the raw binary data?
Have you tried using the function File->Export response to file? It should NOT be related to the use of StringBuffer in the earlier discussion.
The problem with that is that its not just the response I'm interested in, it's the content of a POST, the POST header, the whole lot.
For the time being I've altered the Export Messages to File function to export bodies as rawBytes (using the getBytes() function instead of the toString() function).
It's a good enough fix for me.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.