comment on

HTTP::Message/HTTP::Response/HTTP::Response, ->content should always encoded in bytes ( octets ie 8-bit)


$ perl -MHTTP::Message -e" $a = HTTP::Message->new; $a->content( chr(5
+00) )"
HTTP::Message content must be bytes at -e line 1

$ perl -e"print utf8::is_utf8( chr(500) )"
1
[download]

It relies on utf8::downgrade to check

$success = utf8::downgrade($string[, FAIL_OK])
[download]
Converts in-place the internal octet sequence in *UTF-X* to the equivalent octet sequence in the native encoding (Latin-1 or EBCDIC). *$string* already encoded as native 8 bit does no harm. Can be used to make sure that the UTF-8 flag is off, e.g. when you want to make sure that the substr() or length() function works with the usually faster byte algorithm.

In reply to Re: Size and anatomy of an HTTP response by Anonymous Monk
in thread Size and anatomy of an HTTP response by Discipulus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks