Parents (Total: 31)

The searched file hash is included in 31 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
SHA-1	0EE16B3E1E53E17987D78DD8A903FA6227E6D638
snap-authority	canonical
snap-filename	shY22YTZ3RhJJDOj0MfmShTNZTEb1Jiq_34087.snap
snap-id	shY22YTZ3RhJJDOj0MfmShTNZTEb1Jiq_34087
snap-name	maas
snap-publisher-id	canonical
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2021-10-01T19:38:45.657627Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/shY22YTZ3RhJJDOj0MfmShTNZTEb1Jiq_34087.snap

Key	Value
MD5	5A8923062E3825382829D2CD66956EB1
PackageArch	noarch
PackageDescription	An 'HTTP::Message' object contains some headers and a content body. The following methods are available: * $mess = HTTP::Message->new * $mess = HTTP::Message->new( $headers ) * $mess = HTTP::Message->new( $headers, $content ) This constructs a new message object. Normally you would want construct 'HTTP::Request' or 'HTTP::Response' objects instead. The optional $header argument should be a reference to an 'HTTP::Headers' object or a plain array reference of key/value pairs. If an 'HTTP::Headers' object is provided then a copy of it will be embedded into the constructed message, i.e. it will not be owned and can be modified afterwards without affecting the message. The optional $content argument should be a string of bytes. * $mess = HTTP::Message->parse( $str ) This constructs a new message object by parsing the given string. * $mess->headers Returns the embedded 'HTTP::Headers' object. * $mess->headers_as_string * $mess->headers_as_string( $eol ) Call the as_string() method for the headers in the message. This will be the same as $mess->headers->as_string but it will make your program a whole character shorter :-) * $mess->content * $mess->content( $bytes ) The content() method sets the raw content if an argument is given. If no argument is given the content is not touched. In either case the original raw content is returned. If the 'undef' argument is given, the content is reset to its default value, which is an empty string. Note that the content should be a string of bytes. Strings in perl can contain characters outside the range of a byte. The 'Encode' module can be used to turn such strings into a string of bytes. * $mess->add_content( $bytes ) The add_content() methods appends more data bytes to the end of the current content buffer. * $mess->add_content_utf8( $string ) The add_content_utf8() method appends the UTF-8 bytes representing the string to the end of the current content buffer. * $mess->content_ref * $mess->content_ref( \$bytes ) The content_ref() method will return a reference to content buffer string. It can be more efficient to access the content this way if the content is huge, and it can even be used for direct manipulation of the content, for instance: ${$res->content_ref} =~ s/\bfoo\b/bar/g; This example would modify the content buffer in-place. If an argument is passed it will setup the content to reference some external source. The content() and add_content() methods will automatically dereference scalar references passed this way. For other references content() will return the reference itself and add_content() will refuse to do anything. * $mess->content_charset This returns the charset used by the content in the message. The charset is either found as the charset attribute of the 'Content-Type' header or by guessing. See http://www.w3.org/TR/REC-html40/charset.html#spec-char-encoding for details about how charset is determined. * $mess->decoded_content( %options ) Returns the content with any 'Content-Encoding' undone and, for textual content ('Content-Type' values starting with 'text/', exactly matching 'application/xml', or ending with '+xml'), the raw content's character set decoded into Perl's Unicode string format. Note that this at https://github.com/libwww-perl/HTTP-Message/pull/99 attempt to decode declared character sets for any other content types like 'application/json' or 'application/javascript'. If the 'Content-Encoding' or 'charset' of the message is unknown, this method will fail by returning 'undef'. The following options can be specified. * 'charset' This override the charset parameter for text content. The value 'none' can used to suppress decoding of the charset. * 'default_charset' This override the default charset guessed by content_charset() or if that fails "ISO-8859-1". * 'alt_charset' If decoding fails because the charset specified in the Content-Type header isn't recognized by Perl's Encode module, then try decoding using this charset instead of failing. The 'alt_charset' might be specified as 'none' to simply return the string without any decoding of charset as alternative. * 'charset_strict' Abort decoding if malformed characters is found in the content. By default you get the substitution character ("\x{FFFD}") in place of malformed characters. * 'raise_error' If TRUE then raise an exception if not able to decode content. Reason might be that the specified 'Content-Encoding' or 'charset' is not supported. If this option is FALSE, then decoded_content() will return 'undef' on errors, but will still set $@. * 'ref' If TRUE then a reference to decoded content is returned. This might be more efficient in cases where the decoded content is identical to the raw content as no data copying is required in this case. * $mess->decodable * HTTP::Message::decodable() This returns the encoding identifiers that decoded_content() can process. In scalar context returns a comma separated string of identifiers. This value is suitable for initializing the 'Accept-Encoding' request header field. * $mess->decode This method tries to replace the content of the message with the decoded version and removes the 'Content-Encoding' header. Returns TRUE if successful and FALSE if not. If the message does not have a 'Content-Encoding' header this method does nothing and returns TRUE. Note that the content of the message is still bytes after this method has been called and you still need to call decoded_content() if you want to process its content as a string. * $mess->encode( $encoding, ... ) Apply the given encodings to the content of the message. Returns TRUE if successful. The "identity" (non-)encoding is always supported; other currently supported encodings, subject to availability of required additional modules, are "gzip", "deflate", "x-bzip2" and "base64". A successful call to this function will set the 'Content-Encoding' header. Note that 'multipart/*' or 'message/*' messages can't be encoded and this method will croak if you try. * $mess->parts * $mess->parts( @parts ) * $mess->parts( \@parts ) Messages can be composite, i.e. contain other messages. The composite messages have a content type of 'multipart/*' or 'message/*'. This method give access to the contained messages. The argumentless form will return a list of 'HTTP::Message' objects. If the content type of $msg is not 'multipart/*' or 'message/*' then this will return the empty list. In scalar context only the first object is returned. The returned message parts should be regarded as read-only (future versions of this library might make it possible to modify the parent by modifying the parts). If the content type of $msg is 'message/*' then there will only be one part returned. If the content type is 'message/http', then the return value will be either an 'HTTP::Request' or an 'HTTP::Response' object. If a @parts argument is given, then the content of the message will be modified. The array reference form is provided so that an empty list can be provided. The @parts array should contain 'HTTP::Message' objects. The @parts objects are owned by $mess after this call and should not be modified or made part of other messages. When updating the message with this method and the old content type of $mess is not 'multipart/*' or 'message/*', then the content type is set to 'multipart/mixed' and all other content headers are cleared. This method will croak if the content type is 'message/*' and more than one part is provided. * $mess->add_part( $part ) This will add a part to a message. The $part argument should be another 'HTTP::Message' object. If the previous content type of $mess is not 'multipart/*' then the old content (together with all content headers) will be made part #1 and the content type made 'multipart/mixed' before the new part is added. The $part object is owned by $mess after this call and should not be modified or made part of other messages. There is no return value. * $mess->clear Will clear the headers and set the content to the empty string. There is no return value * $mess->protocol * $mess->protocol( $proto ) Sets the HTTP protocol used for the message. The protocol() is a string like 'HTTP/1.0' or 'HTTP/1.1'. * $mess->clone Returns a copy of the message object. * $mess->as_string * $mess->as_string( $eol ) Returns the message formatted as a single string. The optional $eol parameter specifies the line ending sequence to use. The default is "\n". If no $eol is given then as_string will ensure that the returned string is newline terminated (even when the message content is not). No extra newline is appended if an explicit $eol is passed. * $mess->dump( %opt ) Returns the message formatted as a string. In void context print the string. This differs from '$mess->as_string' in that it escapes the bytes of the content so that it's safe to print them and it limits how much content to print. The escapes syntax used is the same as for Perl's double quoted strings. If there is no content the string "(no content)" is shown in its place. Options to influence the output can be passed as key/value pairs. The following options are recognized: * maxlength => $num How much of the content to show. The default is 512. Set this to 0 for unlimited. If the content is longer then the string is chopped at the limit and the string "...\n(### more bytes not shown)" appended. * no_content => $str Replaces the "(no content)" marker. * prefix => $str A string that will be prefixed to each line of the dump. All methods unknown to 'HTTP::Message' itself are delegated to the 'HTTP::Headers' object that is part of every message. This allows convenient access to these methods. Refer to HTTP::Headers for details of these methods: $mess->header( $field => $val ) $mess->push_header( $field => $val ) $mess->init_header( $field => $val ) $mess->remove_header( $field ) $mess->remove_content_headers $mess->header_field_names $mess->scan( \&doit ) $mess->date $mess->expires $mess->if_modified_since $mess->if_unmodified_since $mess->last_modified $mess->content_type $mess->content_encoding $mess->content_length $mess->content_language $mess->title $mess->user_agent $mess->server $mess->from $mess->referer $mess->www_authenticate $mess->authorization $mess->proxy_authorization $mess->authorization_basic $mess->proxy_authorization_basic
PackageName	perl-HTTP-Message
PackageRelease	lp153.58.1
PackageVersion	6.36
SHA-1	132B17F676815B3C57EF168C0FFBA07373651146
SHA-256	34A17404A6C97F9BFF24A5AFA7C276FD39F057D943AE47C6F3EA4DD7729689CB

Key	Value
SHA-1	19AE79E2FF7AD00785DE228B0DF2926337BCE535
snap-authority	canonical
snap-filename	tIrcA87dMWthuDORCCRU0VpidK5SBVOc_10512.snap
snap-id	tIrcA87dMWthuDORCCRU0VpidK5SBVOc_10512
snap-name	inkscape
snap-publisher-id	KF4DYZawKZ4srIyRy4IeH8slnKUwKgpm
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2021-07-26T04:32:37.811491Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/tIrcA87dMWthuDORCCRU0VpidK5SBVOc_10512.snap

Key	Value
FileName	http://dl-cdn.alpinelinux.org/alpine/latest-stable//main//s390x//perl-http-message-6.36-r0.apk
MD5	0615C05681C4C250617F009665523FC4
SHA-1	3203CAABB206AA84EBB6778E4AD34E625313A357
SHA-256	8BC59C853A9D08A50E9D827B86FED6B305597AB2102457DACAA04AAEC7187C2B
SSDEEP	768:YqVMLu2AsrXdXFErm4tJMCrjUJw3YZqIEnqje/A0RogeAPP0s8:1Qu2vLdKrmgVwEnqq40yess8
TLSH	T1B613F146E047F01DFEE5CEEA92B84D59EC0D3B0802C771B7F759876B4A114B838AD80A

Key	Value
MD5	94D0B030F7038B333FDBDE0F486D49BB
PackageArch	noarch
PackageDescription	An 'HTTP::Message' object contains some headers and a content body. The following methods are available: * $mess = HTTP::Message->new * $mess = HTTP::Message->new( $headers ) * $mess = HTTP::Message->new( $headers, $content ) This constructs a new message object. Normally you would want construct 'HTTP::Request' or 'HTTP::Response' objects instead. The optional $header argument should be a reference to an 'HTTP::Headers' object or a plain array reference of key/value pairs. If an 'HTTP::Headers' object is provided then a copy of it will be embedded into the constructed message, i.e. it will not be owned and can be modified afterwards without affecting the message. The optional $content argument should be a string of bytes. * $mess = HTTP::Message->parse( $str ) This constructs a new message object by parsing the given string. * $mess->headers Returns the embedded 'HTTP::Headers' object. * $mess->headers_as_string * $mess->headers_as_string( $eol ) Call the as_string() method for the headers in the message. This will be the same as $mess->headers->as_string but it will make your program a whole character shorter :-) * $mess->content * $mess->content( $bytes ) The content() method sets the raw content if an argument is given. If no argument is given the content is not touched. In either case the original raw content is returned. If the 'undef' argument is given, the content is reset to its default value, which is an empty string. Note that the content should be a string of bytes. Strings in perl can contain characters outside the range of a byte. The 'Encode' module can be used to turn such strings into a string of bytes. * $mess->add_content( $bytes ) The add_content() methods appends more data bytes to the end of the current content buffer. * $mess->add_content_utf8( $string ) The add_content_utf8() method appends the UTF-8 bytes representing the string to the end of the current content buffer. * $mess->content_ref * $mess->content_ref( \$bytes ) The content_ref() method will return a reference to content buffer string. It can be more efficient to access the content this way if the content is huge, and it can even be used for direct manipulation of the content, for instance: ${$res->content_ref} =~ s/\bfoo\b/bar/g; This example would modify the content buffer in-place. If an argument is passed it will setup the content to reference some external source. The content() and add_content() methods will automatically dereference scalar references passed this way. For other references content() will return the reference itself and add_content() will refuse to do anything. * $mess->content_charset This returns the charset used by the content in the message. The charset is either found as the charset attribute of the 'Content-Type' header or by guessing. See http://www.w3.org/TR/REC-html40/charset.html#spec-char-encoding for details about how charset is determined. * $mess->decoded_content( %options ) Returns the content with any 'Content-Encoding' undone and, for textual content ('Content-Type' values starting with 'text/', exactly matching 'application/xml', or ending with '+xml'), the raw content's character set decoded into Perl's Unicode string format. Note that this at https://github.com/libwww-perl/HTTP-Message/pull/99 attempt to decode declared character sets for any other content types like 'application/json' or 'application/javascript'. If the 'Content-Encoding' or 'charset' of the message is unknown, this method will fail by returning 'undef'. The following options can be specified. * 'charset' This override the charset parameter for text content. The value 'none' can used to suppress decoding of the charset. * 'default_charset' This override the default charset guessed by content_charset() or if that fails "ISO-8859-1". * 'alt_charset' If decoding fails because the charset specified in the Content-Type header isn't recognized by Perl's Encode module, then try decoding using this charset instead of failing. The 'alt_charset' might be specified as 'none' to simply return the string without any decoding of charset as alternative. * 'charset_strict' Abort decoding if malformed characters is found in the content. By default you get the substitution character ("\x{FFFD}") in place of malformed characters. * 'raise_error' If TRUE then raise an exception if not able to decode content. Reason might be that the specified 'Content-Encoding' or 'charset' is not supported. If this option is FALSE, then decoded_content() will return 'undef' on errors, but will still set $@. * 'ref' If TRUE then a reference to decoded content is returned. This might be more efficient in cases where the decoded content is identical to the raw content as no data copying is required in this case. * $mess->decodable * HTTP::Message::decodable() This returns the encoding identifiers that decoded_content() can process. In scalar context returns a comma separated string of identifiers. This value is suitable for initializing the 'Accept-Encoding' request header field. * $mess->decode This method tries to replace the content of the message with the decoded version and removes the 'Content-Encoding' header. Returns TRUE if successful and FALSE if not. If the message does not have a 'Content-Encoding' header this method does nothing and returns TRUE. Note that the content of the message is still bytes after this method has been called and you still need to call decoded_content() if you want to process its content as a string. * $mess->encode( $encoding, ... ) Apply the given encodings to the content of the message. Returns TRUE if successful. The "identity" (non-)encoding is always supported; other currently supported encodings, subject to availability of required additional modules, are "gzip", "deflate", "x-bzip2" and "base64". A successful call to this function will set the 'Content-Encoding' header. Note that 'multipart/*' or 'message/*' messages can't be encoded and this method will croak if you try. * $mess->parts * $mess->parts( @parts ) * $mess->parts( \@parts ) Messages can be composite, i.e. contain other messages. The composite messages have a content type of 'multipart/*' or 'message/*'. This method give access to the contained messages. The argumentless form will return a list of 'HTTP::Message' objects. If the content type of $msg is not 'multipart/*' or 'message/*' then this will return the empty list. In scalar context only the first object is returned. The returned message parts should be regarded as read-only (future versions of this library might make it possible to modify the parent by modifying the parts). If the content type of $msg is 'message/*' then there will only be one part returned. If the content type is 'message/http', then the return value will be either an 'HTTP::Request' or an 'HTTP::Response' object. If a @parts argument is given, then the content of the message will be modified. The array reference form is provided so that an empty list can be provided. The @parts array should contain 'HTTP::Message' objects. The @parts objects are owned by $mess after this call and should not be modified or made part of other messages. When updating the message with this method and the old content type of $mess is not 'multipart/*' or 'message/*', then the content type is set to 'multipart/mixed' and all other content headers are cleared. This method will croak if the content type is 'message/*' and more than one part is provided. * $mess->add_part( $part ) This will add a part to a message. The $part argument should be another 'HTTP::Message' object. If the previous content type of $mess is not 'multipart/*' then the old content (together with all content headers) will be made part #1 and the content type made 'multipart/mixed' before the new part is added. The $part object is owned by $mess after this call and should not be modified or made part of other messages. There is no return value. * $mess->clear Will clear the headers and set the content to the empty string. There is no return value * $mess->protocol * $mess->protocol( $proto ) Sets the HTTP protocol used for the message. The protocol() is a string like 'HTTP/1.0' or 'HTTP/1.1'. * $mess->clone Returns a copy of the message object. * $mess->as_string * $mess->as_string( $eol ) Returns the message formatted as a single string. The optional $eol parameter specifies the line ending sequence to use. The default is "\n". If no $eol is given then as_string will ensure that the returned string is newline terminated (even when the message content is not). No extra newline is appended if an explicit $eol is passed. * $mess->dump( %opt ) Returns the message formatted as a string. In void context print the string. This differs from '$mess->as_string' in that it escapes the bytes of the content so that it's safe to print them and it limits how much content to print. The escapes syntax used is the same as for Perl's double quoted strings. If there is no content the string "(no content)" is shown in its place. Options to influence the output can be passed as key/value pairs. The following options are recognized: * maxlength => $num How much of the content to show. The default is 512. Set this to 0 for unlimited. If the content is longer then the string is chopped at the limit and the string "...\n(### more bytes not shown)" appended. * no_content => $str Replaces the "(no content)" marker. * prefix => $str A string that will be prefixed to each line of the dump. All methods unknown to 'HTTP::Message' itself are delegated to the 'HTTP::Headers' object that is part of every message. This allows convenient access to these methods. Refer to HTTP::Headers for details of these methods: $mess->header( $field => $val ) $mess->push_header( $field => $val ) $mess->init_header( $field => $val ) $mess->remove_header( $field ) $mess->remove_content_headers $mess->header_field_names $mess->scan( \&doit ) $mess->date $mess->expires $mess->if_modified_since $mess->if_unmodified_since $mess->last_modified $mess->content_type $mess->content_encoding $mess->content_length $mess->content_language $mess->title $mess->user_agent $mess->server $mess->from $mess->referer $mess->www_authenticate $mess->authorization $mess->proxy_authorization $mess->authorization_basic $mess->proxy_authorization_basic
PackageName	perl-HTTP-Message
PackageRelease	lp152.58.1
PackageVersion	6.36
SHA-1	3482023E4B51C49422DF082B740973F7D026EC12
SHA-256	A2AD98C48EC44E5D61E736E87D5E80515DE875FF554A76512ABC842F1C6AF68E

Key	Value
MD5	0726D2F577310335ECF282B22C91A728
PackageArch	noarch
PackageDescription	An 'HTTP::Message' object contains some headers and a content body. The following methods are available: * $mess = HTTP::Message->new * $mess = HTTP::Message->new( $headers ) * $mess = HTTP::Message->new( $headers, $content ) This constructs a new message object. Normally you would want construct 'HTTP::Request' or 'HTTP::Response' objects instead. The optional $header argument should be a reference to an 'HTTP::Headers' object or a plain array reference of key/value pairs. If an 'HTTP::Headers' object is provided then a copy of it will be embedded into the constructed message, i.e. it will not be owned and can be modified afterwards without affecting the message. The optional $content argument should be a string of bytes. * $mess = HTTP::Message->parse( $str ) This constructs a new message object by parsing the given string. * $mess->headers Returns the embedded 'HTTP::Headers' object. * $mess->headers_as_string * $mess->headers_as_string( $eol ) Call the as_string() method for the headers in the message. This will be the same as $mess->headers->as_string but it will make your program a whole character shorter :-) * $mess->content * $mess->content( $bytes ) The content() method sets the raw content if an argument is given. If no argument is given the content is not touched. In either case the original raw content is returned. If the 'undef' argument is given, the content is reset to its default value, which is an empty string. Note that the content should be a string of bytes. Strings in perl can contain characters outside the range of a byte. The 'Encode' module can be used to turn such strings into a string of bytes. * $mess->add_content( $bytes ) The add_content() methods appends more data bytes to the end of the current content buffer. * $mess->add_content_utf8( $string ) The add_content_utf8() method appends the UTF-8 bytes representing the string to the end of the current content buffer. * $mess->content_ref * $mess->content_ref( \$bytes ) The content_ref() method will return a reference to content buffer string. It can be more efficient to access the content this way if the content is huge, and it can even be used for direct manipulation of the content, for instance: ${$res->content_ref} =~ s/\bfoo\b/bar/g; This example would modify the content buffer in-place. If an argument is passed it will setup the content to reference some external source. The content() and add_content() methods will automatically dereference scalar references passed this way. For other references content() will return the reference itself and add_content() will refuse to do anything. * $mess->content_charset This returns the charset used by the content in the message. The charset is either found as the charset attribute of the 'Content-Type' header or by guessing. See http://www.w3.org/TR/REC-html40/charset.html#spec-char-encoding for details about how charset is determined. * $mess->decoded_content( %options ) Returns the content with any 'Content-Encoding' undone and, for textual content ('Content-Type' values starting with 'text/', exactly matching 'application/xml', or ending with '+xml'), the raw content's character set decoded into Perl's Unicode string format. Note that this at https://github.com/libwww-perl/HTTP-Message/pull/99 attempt to decode declared character sets for any other content types like 'application/json' or 'application/javascript'. If the 'Content-Encoding' or 'charset' of the message is unknown, this method will fail by returning 'undef'. The following options can be specified. * 'charset' This override the charset parameter for text content. The value 'none' can used to suppress decoding of the charset. * 'default_charset' This override the default charset guessed by content_charset() or if that fails "ISO-8859-1". * 'alt_charset' If decoding fails because the charset specified in the Content-Type header isn't recognized by Perl's Encode module, then try decoding using this charset instead of failing. The 'alt_charset' might be specified as 'none' to simply return the string without any decoding of charset as alternative. * 'charset_strict' Abort decoding if malformed characters is found in the content. By default you get the substitution character ("\x{FFFD}") in place of malformed characters. * 'raise_error' If TRUE then raise an exception if not able to decode content. Reason might be that the specified 'Content-Encoding' or 'charset' is not supported. If this option is FALSE, then decoded_content() will return 'undef' on errors, but will still set $@. * 'ref' If TRUE then a reference to decoded content is returned. This might be more efficient in cases where the decoded content is identical to the raw content as no data copying is required in this case. * $mess->decodable * HTTP::Message::decodable() This returns the encoding identifiers that decoded_content() can process. In scalar context returns a comma separated string of identifiers. This value is suitable for initializing the 'Accept-Encoding' request header field. * $mess->decode This method tries to replace the content of the message with the decoded version and removes the 'Content-Encoding' header. Returns TRUE if successful and FALSE if not. If the message does not have a 'Content-Encoding' header this method does nothing and returns TRUE. Note that the content of the message is still bytes after this method has been called and you still need to call decoded_content() if you want to process its content as a string. * $mess->encode( $encoding, ... ) Apply the given encodings to the content of the message. Returns TRUE if successful. The "identity" (non-)encoding is always supported; other currently supported encodings, subject to availability of required additional modules, are "gzip", "deflate", "x-bzip2" and "base64". A successful call to this function will set the 'Content-Encoding' header. Note that 'multipart/*' or 'message/*' messages can't be encoded and this method will croak if you try. * $mess->parts * $mess->parts( @parts ) * $mess->parts( \@parts ) Messages can be composite, i.e. contain other messages. The composite messages have a content type of 'multipart/*' or 'message/*'. This method give access to the contained messages. The argumentless form will return a list of 'HTTP::Message' objects. If the content type of $msg is not 'multipart/*' or 'message/*' then this will return the empty list. In scalar context only the first object is returned. The returned message parts should be regarded as read-only (future versions of this library might make it possible to modify the parent by modifying the parts). If the content type of $msg is 'message/*' then there will only be one part returned. If the content type is 'message/http', then the return value will be either an 'HTTP::Request' or an 'HTTP::Response' object. If a @parts argument is given, then the content of the message will be modified. The array reference form is provided so that an empty list can be provided. The @parts array should contain 'HTTP::Message' objects. The @parts objects are owned by $mess after this call and should not be modified or made part of other messages. When updating the message with this method and the old content type of $mess is not 'multipart/*' or 'message/*', then the content type is set to 'multipart/mixed' and all other content headers are cleared. This method will croak if the content type is 'message/*' and more than one part is provided. * $mess->add_part( $part ) This will add a part to a message. The $part argument should be another 'HTTP::Message' object. If the previous content type of $mess is not 'multipart/*' then the old content (together with all content headers) will be made part #1 and the content type made 'multipart/mixed' before the new part is added. The $part object is owned by $mess after this call and should not be modified or made part of other messages. There is no return value. * $mess->clear Will clear the headers and set the content to the empty string. There is no return value * $mess->protocol * $mess->protocol( $proto ) Sets the HTTP protocol used for the message. The protocol() is a string like 'HTTP/1.0' or 'HTTP/1.1'. * $mess->clone Returns a copy of the message object. * $mess->as_string * $mess->as_string( $eol ) Returns the message formatted as a single string. The optional $eol parameter specifies the line ending sequence to use. The default is "\n". If no $eol is given then as_string will ensure that the returned string is newline terminated (even when the message content is not). No extra newline is appended if an explicit $eol is passed. * $mess->dump( %opt ) Returns the message formatted as a string. In void context print the string. This differs from '$mess->as_string' in that it escapes the bytes of the content so that it's safe to print them and it limits how much content to print. The escapes syntax used is the same as for Perl's double quoted strings. If there is no content the string "(no content)" is shown in its place. Options to influence the output can be passed as key/value pairs. The following options are recognized: * maxlength => $num How much of the content to show. The default is 512. Set this to 0 for unlimited. If the content is longer then the string is chopped at the limit and the string "...\n(### more bytes not shown)" appended. * no_content => $str Replaces the "(no content)" marker. * prefix => $str A string that will be prefixed to each line of the dump. All methods unknown to 'HTTP::Message' itself are delegated to the 'HTTP::Headers' object that is part of every message. This allows convenient access to these methods. Refer to HTTP::Headers for details of these methods: $mess->header( $field => $val ) $mess->push_header( $field => $val ) $mess->init_header( $field => $val ) $mess->remove_header( $field ) $mess->remove_content_headers $mess->header_field_names $mess->scan( \&doit ) $mess->date $mess->expires $mess->if_modified_since $mess->if_unmodified_since $mess->last_modified $mess->content_type $mess->content_encoding $mess->content_length $mess->content_language $mess->title $mess->user_agent $mess->server $mess->from $mess->referer $mess->www_authenticate $mess->authorization $mess->proxy_authorization $mess->authorization_basic $mess->proxy_authorization_basic
PackageName	perl-HTTP-Message
PackageRelease	58.1
PackageVersion	6.36
SHA-1	3B3BB398DD3DD7613BA53AA4E11730DC48E24D67
SHA-256	183250C03E03287AD0B577E7CE41599BE5733A0F6E446357A4411ADA005A8302

Key	Value
MD5	FA869805E1FC6C9E744602756A8FAA0D
PackageArch	noarch
PackageDescription	An 'HTTP::Message' object contains some headers and a content body. The following methods are available: * $mess = HTTP::Message->new * $mess = HTTP::Message->new( $headers ) * $mess = HTTP::Message->new( $headers, $content ) This constructs a new message object. Normally you would want construct 'HTTP::Request' or 'HTTP::Response' objects instead. The optional $header argument should be a reference to an 'HTTP::Headers' object or a plain array reference of key/value pairs. If an 'HTTP::Headers' object is provided then a copy of it will be embedded into the constructed message, i.e. it will not be owned and can be modified afterwards without affecting the message. The optional $content argument should be a string of bytes. * $mess = HTTP::Message->parse( $str ) This constructs a new message object by parsing the given string. * $mess->headers Returns the embedded 'HTTP::Headers' object. * $mess->headers_as_string * $mess->headers_as_string( $eol ) Call the as_string() method for the headers in the message. This will be the same as $mess->headers->as_string but it will make your program a whole character shorter :-) * $mess->content * $mess->content( $bytes ) The content() method sets the raw content if an argument is given. If no argument is given the content is not touched. In either case the original raw content is returned. If the 'undef' argument is given, the content is reset to its default value, which is an empty string. Note that the content should be a string of bytes. Strings in perl can contain characters outside the range of a byte. The 'Encode' module can be used to turn such strings into a string of bytes. * $mess->add_content( $bytes ) The add_content() methods appends more data bytes to the end of the current content buffer. * $mess->add_content_utf8( $string ) The add_content_utf8() method appends the UTF-8 bytes representing the string to the end of the current content buffer. * $mess->content_ref * $mess->content_ref( \$bytes ) The content_ref() method will return a reference to content buffer string. It can be more efficient to access the content this way if the content is huge, and it can even be used for direct manipulation of the content, for instance: ${$res->content_ref} =~ s/\bfoo\b/bar/g; This example would modify the content buffer in-place. If an argument is passed it will setup the content to reference some external source. The content() and add_content() methods will automatically dereference scalar references passed this way. For other references content() will return the reference itself and add_content() will refuse to do anything. * $mess->content_charset This returns the charset used by the content in the message. The charset is either found as the charset attribute of the 'Content-Type' header or by guessing. See http://www.w3.org/TR/REC-html40/charset.html#spec-char-encoding for details about how charset is determined. * $mess->decoded_content( %options ) Returns the content with any 'Content-Encoding' undone and, for textual content ('Content-Type' values starting with 'text/', exactly matching 'application/xml', or ending with '+xml'), the raw content's character set decoded into Perl's Unicode string format. Note that this at https://github.com/libwww-perl/HTTP-Message/pull/99 attempt to decode declared character sets for any other content types like 'application/json' or 'application/javascript'. If the 'Content-Encoding' or 'charset' of the message is unknown, this method will fail by returning 'undef'. The following options can be specified. * 'charset' This override the charset parameter for text content. The value 'none' can used to suppress decoding of the charset. * 'default_charset' This override the default charset guessed by content_charset() or if that fails "ISO-8859-1". * 'alt_charset' If decoding fails because the charset specified in the Content-Type header isn't recognized by Perl's Encode module, then try decoding using this charset instead of failing. The 'alt_charset' might be specified as 'none' to simply return the string without any decoding of charset as alternative. * 'charset_strict' Abort decoding if malformed characters is found in the content. By default you get the substitution character ("\x{FFFD}") in place of malformed characters. * 'raise_error' If TRUE then raise an exception if not able to decode content. Reason might be that the specified 'Content-Encoding' or 'charset' is not supported. If this option is FALSE, then decoded_content() will return 'undef' on errors, but will still set $@. * 'ref' If TRUE then a reference to decoded content is returned. This might be more efficient in cases where the decoded content is identical to the raw content as no data copying is required in this case. * $mess->decodable * HTTP::Message::decodable() This returns the encoding identifiers that decoded_content() can process. In scalar context returns a comma separated string of identifiers. This value is suitable for initializing the 'Accept-Encoding' request header field. * $mess->decode This method tries to replace the content of the message with the decoded version and removes the 'Content-Encoding' header. Returns TRUE if successful and FALSE if not. If the message does not have a 'Content-Encoding' header this method does nothing and returns TRUE. Note that the content of the message is still bytes after this method has been called and you still need to call decoded_content() if you want to process its content as a string. * $mess->encode( $encoding, ... ) Apply the given encodings to the content of the message. Returns TRUE if successful. The "identity" (non-)encoding is always supported; other currently supported encodings, subject to availability of required additional modules, are "gzip", "deflate", "x-bzip2" and "base64". A successful call to this function will set the 'Content-Encoding' header. Note that 'multipart/*' or 'message/*' messages can't be encoded and this method will croak if you try. * $mess->parts * $mess->parts( @parts ) * $mess->parts( \@parts ) Messages can be composite, i.e. contain other messages. The composite messages have a content type of 'multipart/*' or 'message/*'. This method give access to the contained messages. The argumentless form will return a list of 'HTTP::Message' objects. If the content type of $msg is not 'multipart/*' or 'message/*' then this will return the empty list. In scalar context only the first object is returned. The returned message parts should be regarded as read-only (future versions of this library might make it possible to modify the parent by modifying the parts). If the content type of $msg is 'message/*' then there will only be one part returned. If the content type is 'message/http', then the return value will be either an 'HTTP::Request' or an 'HTTP::Response' object. If a @parts argument is given, then the content of the message will be modified. The array reference form is provided so that an empty list can be provided. The @parts array should contain 'HTTP::Message' objects. The @parts objects are owned by $mess after this call and should not be modified or made part of other messages. When updating the message with this method and the old content type of $mess is not 'multipart/*' or 'message/*', then the content type is set to 'multipart/mixed' and all other content headers are cleared. This method will croak if the content type is 'message/*' and more than one part is provided. * $mess->add_part( $part ) This will add a part to a message. The $part argument should be another 'HTTP::Message' object. If the previous content type of $mess is not 'multipart/*' then the old content (together with all content headers) will be made part #1 and the content type made 'multipart/mixed' before the new part is added. The $part object is owned by $mess after this call and should not be modified or made part of other messages. There is no return value. * $mess->clear Will clear the headers and set the content to the empty string. There is no return value * $mess->protocol * $mess->protocol( $proto ) Sets the HTTP protocol used for the message. The protocol() is a string like 'HTTP/1.0' or 'HTTP/1.1'. * $mess->clone Returns a copy of the message object. * $mess->as_string * $mess->as_string( $eol ) Returns the message formatted as a single string. The optional $eol parameter specifies the line ending sequence to use. The default is "\n". If no $eol is given then as_string will ensure that the returned string is newline terminated (even when the message content is not). No extra newline is appended if an explicit $eol is passed. * $mess->dump( %opt ) Returns the message formatted as a string. In void context print the string. This differs from '$mess->as_string' in that it escapes the bytes of the content so that it's safe to print them and it limits how much content to print. The escapes syntax used is the same as for Perl's double quoted strings. If there is no content the string "(no content)" is shown in its place. Options to influence the output can be passed as key/value pairs. The following options are recognized: * maxlength => $num How much of the content to show. The default is 512. Set this to 0 for unlimited. If the content is longer then the string is chopped at the limit and the string "...\n(### more bytes not shown)" appended. * no_content => $str Replaces the "(no content)" marker. * prefix => $str A string that will be prefixed to each line of the dump. All methods unknown to 'HTTP::Message' itself are delegated to the 'HTTP::Headers' object that is part of every message. This allows convenient access to these methods. Refer to HTTP::Headers for details of these methods: $mess->header( $field => $val ) $mess->push_header( $field => $val ) $mess->init_header( $field => $val ) $mess->remove_header( $field ) $mess->remove_content_headers $mess->header_field_names $mess->scan( \&doit ) $mess->date $mess->expires $mess->if_modified_since $mess->if_unmodified_since $mess->last_modified $mess->content_type $mess->content_encoding $mess->content_length $mess->content_language $mess->title $mess->user_agent $mess->server $mess->from $mess->referer $mess->www_authenticate $mess->authorization $mess->proxy_authorization $mess->authorization_basic $mess->proxy_authorization_basic
PackageName	perl-HTTP-Message
PackageRelease	58.1
PackageVersion	6.36
SHA-1	47D7E33808ED9902A2EB7E1880572903BDD9544B
SHA-256	A0B6A8D9C7A558CA7F7EB876AB4DDE6845101B28AD0382EF70E3155E36D62337

Key	Value
SHA-1	497D0F69DF615697BCF71A9B6D5F4DE8D010AFB5
snap-authority	canonical
snap-filename	tIrcA87dMWthuDORCCRU0VpidK5SBVOc_10555.snap
snap-id	tIrcA87dMWthuDORCCRU0VpidK5SBVOc_10555
snap-name	inkscape
snap-publisher-id	KF4DYZawKZ4srIyRy4IeH8slnKUwKgpm
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2021-07-26T04:32:37.811491Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/tIrcA87dMWthuDORCCRU0VpidK5SBVOc_10555.snap

Key	Value
FileName	http://dl-cdn.alpinelinux.org/alpine/latest-stable//main//x86//perl-http-message-6.36-r0.apk
MD5	7FD02E1F3B01AF7B304DAEECF354C6E7
SHA-1	4A52844DE4B6245D5F5F5847EEEC451D128C344D
SHA-256	CBE6C5DC3254C6783D8FBDD0BA9AA225107CE30805EE6236BDA96A07DB1B4E14
SSDEEP	768:ItG5DVMLu2AsrXdXFErm4tJMCrjUJw3Y6qIEnqje/A0RogeAPP0sZ:fDQu2vLdKrmgVFEnqq40yessZ
TLSH	T18313F185A08BF02DFDA18EEE91B95D59EC0C3B4406D7B1BBF65D835B491107878ED80B

Key	Value
SHA-1	543F9310C8DC21E465594100F7FDE066BE3FDD31
snap-authority	canonical
snap-filename	CSo0CbPKGdEinFT3GPabArcrDYP3cto7_22.snap
snap-id	CSo0CbPKGdEinFT3GPabArcrDYP3cto7_22
snap-name	kommit
snap-publisher-id	2rsYZu6kqYVFsSejExu4YENdXQEO40Xb
snap-signkey	BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul
snap-timestamp	2023-04-20T18:13:01.669427Z
source-url	https://api.snapcraft.io/api/v1/snaps/download/CSo0CbPKGdEinFT3GPabArcrDYP3cto7_22.snap