GSP/Panel
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added Cyg-Win

Browse source
This commit is contained in:
Frank Harris 2026-06-06 18:46:40 -04:00
parent 82cbc206eb
commit 413c315806
10586 changed files with 3806249 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

103
Agent-Windows/OGP64/usr/share/doc/perl-HTTP-Message/CONTRIBUTORS Normal file
View file

@ -0,0 +1,103 @@
# HTTP-MESSAGE CONTRIBUTORS #
This is the (likely incomplete) list of people who have helped
make this distribution what it is, either via code contributions,
patches, bug reports, help with troubleshooting, etc. A huge
'thank you' to all of them.
* Adam Kennedy
* Adam Sjogren
* Alexey Tourbin
* Alex Kapranoff
* amire80
* Andreas J. Koenig
* Andrei Grechkin
* bayashi
* Bill Mann
* Brendan Byrd
* Bron Gondwana
* Chase Whitener
* Christopher J. Madsen
* chromatic
* copilot-swe-agent[bot]
* Dan Book
* Daniel Hedlund
* Daniel Trizen
* David E. Wheeler
* DAVIDRW
* David Steinbrunner
* dependabot[bot]
* Dorian Taylor
* Eric Wastl
* Father Chrysostomos
* Felipe Gasper
* FWILES
* Galen Huntington
* Gavin Peters
* Gisle Aas
* Graeme Thompson
* Graham Knop
* Håkon Hægland
* Hans-H. Froehlich
* Ian Kilgore
* Jacob J
* Jakub Skory
* Jakub Wilk
* James Raspass
* jefflee
* Jerome Eteve
* john9art
* jonasbn
* Julien Fiegehenn
* Karen Etheridge
* Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯
* Mark Overmeer
* Mark Stosberg
* Martin H. Sluka
* Matthew Chae
* Max Maischein
* Michael Schout
* Michal Josef Špaček
* Mickey Nasriachi
* Mike Schilli
* murphy
* nanto_vi, TOYAMA Nao
* Neil Bowers
* Olaf Alders
* Olivier Mengué
* Ondrej Hanak
* openstrike
* Peter Rabbitson
* phrstbrn
* Robert Rothenberg
* Robert Stone
* Rolf Grossmann
* ruff
* sasao
* Saturday Walkers Club
* Sean M. Burke
* Slaven Rezic
* Spiros Denaxas
* Steve Hay
* Tatsuhiko Miyagawa
* Theo van Hoesel
* Tigran
* Tobias Leich
* Todd Lipcon
* tokuhirom
* Tom Hukins
* Tony Finch
* Toru Yamaguchi
* tzccinct
* uid39246
* Ville Skyttä
* Vít Strádal
* Wesley Schwengle
* William Storey
* yoshikazusawa
* Yuri Karaban
* Zakariyya Mughal
* Zefram

256
Agent-Windows/OGP64/usr/share/doc/perl-HTTP-Message/Changes Normal file
View file

@ -0,0 +1,256 @@
Revision history for HTTP-Message
7.01 2025-10-19 17:22:21Z
- Fix HTTP::Response and HTTP::Request as_string/parse commutativity issue
#62959 (GH#212) (Copilot)
- Fix few minor typos (GH#202) (Yoshikazu Sawa)
7.00 2024-10-07 15:31:56Z
- Stop transforming LF into CRLF. Fixes #69 (GH#196) (Olaf Alders)
6.46 2024-05-27 18:58:16Z
- Update several status codes to RFC 9110 (GH#197) (Wesley Schwengle)
6.45 2023-09-27 14:27:31Z
- Allow for file ownership conflicts with Docker and GitHub Actions
(GH#193) (Olaf Alders)
- Add the 'status_code' function for getting all status codes as hash
(GH#194) (Dai Okabayashi)
6.44 2022-10-26 20:49:00Z
- Made the Clone module a hard requirement, so we don't have to
provide a fallback function for HTTP::Headers::clone().
We require at least Clone 0.46, as that release now supports
Perl back to 5.8.1, just like us. (GH#184) (Neil Bowers)
- Import clone from Clone rather than inheriting (GH#189) (Graham Knop)
- Made the Compress::Raw::Zlib 2.062 module minimal required
version. (GH#190) (Jakub 'q84fh' Skory)
6.43 2022-10-22 14:50:35Z
- Remove dependency to IO::Uncompress::Bunzip2. (Michal Josef Spacek)
- Remove dependency to IO::Uncompress::Gunzip. (Michal Josef Spacek)
6.42 2022-10-18 13:53:22Z
- We now don't consider the Content-Location header when asked
for the base URI. RFC 7231 says we shouldn't. (GH#51) (Neil Bowers)
- Increased the (max) buffer size for read() when processing form data,
from 2048 to 8192. This was suggested in RT#105184, as it improved
performance for them. (GH#59) (Neil Bowers)
6.41 2022-10-12 15:57:40Z
- Add maximum size for HTTP::Message->decoded_content
This can be used to limit the size of a decompressed HTTP response,
especially when making requests to untrusted or user-specified servers.
The $HTTP::Message::MAXIMUM_BODY_SIZE variable and the ->max_body_size
accessor can set this limit. (GH#181) (Max Maischein)
6.40 2022-10-12 15:45:52Z
- Fixed two typos in the doc, originally reported by FatherC
in RT#90716, ported over as GH#57. (GH#57) (Neil Bowers)
6.39 2022-10-08 13:48:26Z
- Remove Travis config (GH#180) (Olaf Alders)
- Added status_constant_name() which maps status code
to the name of the corresponding constant. (GH#160) (Neil Bowers)
- Updated the doc for status_message() to clarify that it
returns "Not Found" and not "HTTP_NOT_FOUND". (GH#160) (Neil Bowers)
6.38 2022-10-06 21:48:18Z
- Replace "base" with "parent" (GH#176) (James Raspass)
- Replace "print" with "note" in tests (GH#178) (James Raspass)
- Noted that OPTIONS supported was added in 6.1, to the doc
for HTTP::Request::Common. Addresses GH#177. (GH#179) (Neil Bowers)
6.37 2022-06-14 14:08:55Z
- Support for Brotli "br" encoding (GH#163) (trizen and Julien Fiegehenn)
- Don't test Perl > 5.32 on Windows in GH Actions (GH#174) (Olaf Alders)
6.36 2022-01-05 14:39:42Z
- Fix examples in HTTP::Request::Common synopsis: HTTP::Request::Common
does not put headers in an arrayref, unlike HTTP::Request (GH#170) (Karen
Etheridge)
- Update to contributing information (GH#171) (Håkon Hægland)
6.35 2021-11-11 22:10:31Z
- Clarify documentation for decoded_content (GH#166) (Eric Wastl)
6.34 2021-11-08 14:27:36Z
- Catch case of empty name/value in header words split. (GH#168) (Galen Huntington)
6.33 2021-06-28 16:51:58Z
- Allow `can` method to respond to delegated methods (GH#159) (nanto_vi,
TOYAMA Nao)
6.32 2021-05-18 18:54:27Z
- Use File::Spec for MSWin32 on Content-Disposition filename (GH#157)
(tzccinct)
6.31 2021-05-11 18:07:37Z
- Fix test writing to files (GH#156) (Michal Josef Špaček)
6.30 2021-05-10 14:55:55Z
- Don't inherit from Exporter anymore (GH#155) (Max Maischein)
- Remove superfluous Perl version requirement. This module requires Perl
5.6 or newer. (GH#155) (Max Maischein)
6.29 2021-03-06 04:50:34Z
- fix issue with HTTP::Request internal cache for canonical url when using
URI::URL (GH#146) (andrew-grechkin)
6.28 2021-02-19 16:22:13Z
- fix warnings during HTTP::Config->match #62 (GH#152) (Viťas Strádal)
6.27 2021-01-05 03:02:01Z
- Clean up backcompat code (GH#148) (Dan Book)
- Add "308 Permanent Redirect" to is_cacheable_by_default (GH#150) (simbabque)
6.26 2020-09-10 02:34:25Z
- Update comment which explains in which RFC 451 is defined (GH#143) (Olaf
Alders). Reported by Toby Inkster.
- Fix HTTP status descriptions and add 425 Too Early (GH#145) (Dan Book)
6.25 2020-06-28 17:52:12Z
- Don't run Changes test on master in GH actions
- move Clone from required to suggests prerequisite, to re-enable
fatpacking
6.24 2020-05-11 13:15:25Z
- Full release. No changes since TRIAL release 6.23
6.23 2020-05-07 17:57:18Z (TRIAL RELEASE)
- Enable static install (GH#134) (Olaf Alders)
- Support non-string header values that stringify (GH#137) (Will Storey)
6.22 2020-02-24 18:58:07Z
- Full release. No changes since TRIAL release 6.21
6.21 2020-02-19 14:35:09Z (TRIAL RELEASE)
- Bump Encode to latest version (3.01) (GH#129) (Olaf Alders)
- Revert #115 (GH#131) (Olaf Alders)
- Revert (GH#125) "try hard to make a usable file name" (GH#130) (Olaf
Alders)
- Fix JSON request encoding examples in POD (GH#126) (Michael Schout)
- Added support for OPTIONS requests.
6.20 2019-02-05 01:46:39Z (TRIAL RELEASE)
- Fix encoded file names when LC_ALL=C (GH#125) (Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯)
6.19 2019-01-16 15:17:35Z (TRIAL RELEASE)
- Add support for RFC 8187 encoded filenames (GH#115) (Zaki Mughal)
- Fix memoized _uri_canonical #121 (GH#123) (Dorian Taylor)
- Don't overwrite $@ in decodable (gh #80) (GH#118) (mschae94)
- Add support for RFC 8187 encoded filenames (GH#115) (Zaki Mughal)
6.18 2018-06-05 16:29:15Z
- Revert status_message to original code (GH#111) (Theo van Hoesel)
6.17 2018-06-05 01:55:34Z
- Documented status code 451 in the list of constants (GH #104) (Robert Rothenberg)
- Status code 451 is cachable by default, as per RFC 7725 (GH #104) (Robert Rothenberg)
- Add default status_message for unknown status codes (GH#105) (Robert Rothenberg)
- Corrections to the documentation (GH#102) (Jonas B. Nielsen)
6.16 2018-03-28 14:09:17Z
- Update status codes to official IANA list (GH#100) (Theo van Hoesel)
6.15 2018-03-13 13:02:56Z
- Whenever possible, use an absolute four digit year for Time::Local (GH#97)
- Add is_cacheable_by_default() (GH#98) (Theo van Hoesel)
6.14 2017-12-20 22:28:48Z
- Add some useful examples in HTTP::Request (GH #92) (Chase Whitener).
Batch requests are now explained.
- PUT and PATCH docs updated (GH #84) (saturdaywalkers)
- Trim trailing \r from status line so message() doesn't return it (GH #87) (Felipe Gasper)
- Bring test coverage of HTTP::Config to 100% (GH #85) (Pete Houston)
- Add 103 Early Hints to HTTP::Status (GH #94) (Tatsuhiko Miyagawa)
6.13 2017-06-20 01:07:03Z
- Non-TRIAL release of changes found in 6.12
6.12 2017-06-15 18:03:50Z (TRIAL RELEASE)
- If an object is passed to HTTP::Request, it must provide a canonical()
method (Olaf Alders)
- Make sure status messages don't die by checking the status exists before
checking the value range (Kent Fredric, GH #39)
- Add a .mailmap file to clean up the contributors list
- Avoid inconsistent setting of content to undef (Jerome Eteve)
- Simplify the way some methods are created (Tom Hukins)
- Remove some indirect object notation (Chase Whitener)
- Fix example in Pod (Tobias Leich)
- Add support for HTTP PATCH method (Mickey Nasriachi)
6.11 2015-09-09
- fix an undefined value warning in HTTP::Headers::as_string
6.10 2015-07-19
- fix uses of qr/.../m in tests that do not work in 5.8.x
6.09 2015-07-19
- converted all uses of Test.pm to Test::More
- fix uninitialized warning in HTTP::Config (RT#105929)
6.08 2015-07-10
- Resolve new uninitialized warning from
HTTP::Request::Common::request_type_with_data (RT#105787)
6.07 2015-07-09
- Allow subclasses to override the class of parts - it used to be hardcoded
to HTTP::Message. (Gisle Aas, RT#79239)
- Added support for is_client_error, is_server_error to HTTP::Response
(Karen Etheridge)
- Added flatten interface to HTTP::Headers (Tokuhiro Matsuno, GH#5)
- Allow PUT to pass content data via hashrefs just like with POST (Michael
Schilli, GH#9)
- Fix for "Content-Encoding: none" header (Gisle Aas, RT#94882)
- Add support for HTTP status 308, defined in RFC 7238 (Olivier Mengué,
RT#104102)
- drop the use of "use vars" (Karen Etheridge)
6.06 2012-10-21
- More forgiving test on croak message [RT#80302] (Gisle Aas)
- Added test for multipart parsing (Gisle Aas)
- Multipart end boundary doesn't need match a complete line [RT#79239]
(Mark Overmeer)
6.05 2012-10-20
- Updated ignores (Gisle Aas)
- No need to prevent visiting field values starting with '_' (Gisle Aas)
- Report the correct croak caller for delegated methods (Gisle Aas)
- Disallow empty field names or field names containing ':' (Gisle Aas)
- Make the extra std_case entries local to each header (Gisle Aas)
6.04 2012-09-30
- Updated repository URL (Gisle Aas)
- Avoid undef warning for empty content (Gisle Aas)
- Teach $m->content_charset about JSON (Gisle Aas)
- Use the canonical charset name for UTF-16LE (and frieds) (Gisle Aas)
- Add option to override the "(no content)" marker of $m->dump (Gisle Aas)
- Use IO::HTML for <meta> encoding sniffing (Christopher J. Madsen)
- mime_name was introduced in Encode 2.21 (Christopher J. Madsen)
- Remove an unneeded "require" (Tom Hukins)
- Spelling fixes. (Ville Skyttä)
- Sanitized PERL_HTTP_URI_CLASS environment variable. (chromatic)
- Add test from RT#77466 (Martin H. Sluka)
- Fix doc grammo [RT#75831] (Father Chrysostomos)
6.03 2012-02-16
- Support 'bzip2' as alternative to Content-Encoding: x-bzip2. Some
servers seem to return it.
- Make newlines in forms be "\r\n" terminated.
- Added some more status codes.
- Restore perl-5.8.1 compatibility.
6.02 2011-03-20
- Declare dependency on Bunzip2 v2.021 [RT#66593]
6.01 2011-03-07
- Avoid loading XML::Simple to avoid test failures.
- Eliminate the HTML::Entities dependency.
6.00 2011-02-27
- Initial release of HTTP-Message as a separate distribution. There are no
code changes besides incrementing the version number since
libwww-perl-5.837.
- The HTTP::Message module with friends used to be bundled with the
libwww-perl distribution.

411
Agent-Windows/OGP64/usr/share/doc/perl-HTTP-Message/LICENSE Normal file
View file

@ -0,0 +1,411 @@
This software is copyright (c) 1994 by Gisle Aas.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.
Terms of the Perl programming language system itself
a) the GNU General Public License as published by the Free
Software Foundation; either version 1, or (at your option) any
later version, or
b) the "Artistic License"
--- The GNU General Public License, Version 1, February 1989 ---
This software is Copyright (c) 1994 by Gisle Aas.
This is free software, licensed under:
The GNU General Public License, Version 1, February 1989
GNU GENERAL PUBLIC LICENSE
Version 1, February 1989
Copyright (C) 1989 Free Software Foundation, Inc.
<https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The license agreements of most software companies try to keep users
at the mercy of those companies. By contrast, our General Public
License is intended to guarantee your freedom to share and change free
software--to make sure the software is free for all its users. The
General Public License applies to the Free Software Foundation's
software and to any other program whose authors commit to using it.
You can use it for your programs, too.
When we speak of free software, we are referring to freedom, not
price. Specifically, the General Public License is designed to make
sure that you have the freedom to give away or sell copies of free
software, that you receive source code or can get it if you want it,
that you can change the software or use pieces of it in new free
programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if you
distribute copies of the software, or if you modify it.
For example, if you distribute copies of a such a program, whether
gratis or for a fee, you must give the recipients all the rights that
you have. You must make sure that they, too, receive or can get the
source code. And you must tell them their rights.
We protect your rights with two steps: (1) copyright the software, and
(2) offer you this license which gives you legal permission to copy,
distribute and/or modify the software.
Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
that any problems introduced by others will not reflect on the original
authors' reputations.
The precise terms and conditions for copying, distribution and
modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any program or other work which
contains a notice placed by the copyright holder saying it may be
distributed under the terms of this General Public License. The
"Program", below, refers to any such program or work, and a "work based
on the Program" means either the Program or any work containing the
Program or a portion of it, either verbatim or with modifications. Each
licensee is addressed as "you".
1. You may copy and distribute verbatim copies of the Program's source
code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and
disclaimer of warranty; keep intact all the notices that refer to this
General Public License and to the absence of any warranty; and give any
other recipients of the Program a copy of this General Public License
along with the Program. You may charge a fee for the physical act of
transferring a copy.
2. You may modify your copy or copies of the Program or any portion of
it, and copy and distribute such modifications under the terms of Paragraph
1 above, provided that you also do the following:
a) cause the modified files to carry prominent notices stating that
you changed the files and the date of any change; and
b) cause the whole of any work that you distribute or publish, that
in whole or in part contains the Program or any part thereof, either
with or without modifications, to be licensed at no charge to all
third parties under the terms of this General Public License (except
that you may choose to grant warranty protection to some or all
third parties, at your option).
c) If the modified program normally reads commands interactively when
run, you must cause it, when started running for such interactive use
in the simplest and most usual way, to print or display an
announcement including an appropriate copyright notice and a notice
that there is no warranty (or else, saying that you provide a
warranty) and that users may redistribute the program under these
conditions, and telling the user how to view a copy of this General
Public License.
d) You may charge a fee for the physical act of transferring a
copy, and you may at your option offer warranty protection in
exchange for a fee.
Mere aggregation of another independent work with the Program (or its
derivative) on a volume of a storage or distribution medium does not bring
the other work under the scope of these terms.
3. You may copy and distribute the Program (or a portion or derivative of
it, under Paragraph 2) in object code or executable form under the terms of
Paragraphs 1 and 2 above provided that you also do one of the following:
a) accompany it with the complete corresponding machine-readable
source code, which must be distributed under the terms of
Paragraphs 1 and 2 above; or,
b) accompany it with a written offer, valid for at least three
years, to give any third party free (except for a nominal charge
for the cost of distribution) a complete machine-readable copy of the
corresponding source code, to be distributed under the terms of
Paragraphs 1 and 2 above; or,
c) accompany it with the information you received as to where the
corresponding source code may be obtained. (This alternative is
allowed only for noncommercial distribution and only if you
received the program in object code or executable form alone.)
Source code for a work means the preferred form of the work for making
modifications to it. For an executable file, complete source code means
all the source code for all modules it contains; but, as a special
exception, it need not include source code for modules which are standard
libraries that accompany the operating system on which the executable
file runs, or for standard header files or definitions files that
accompany that operating system.
4. You may not copy, modify, sublicense, distribute or transfer the
Program except as expressly provided under this General Public License.
Any attempt otherwise to copy, modify, sublicense, distribute or transfer
the Program is void, and will automatically terminate your rights to use
the Program under this License. However, parties who have received
copies, or rights to use copies, from you under this General Public
License will not have their licenses terminated so long as such parties
remain in full compliance.
5. By copying, distributing or modifying the Program (or any work based
on the Program) you indicate your acceptance of this license to do so,
and all its terms and conditions.
6. Each time you redistribute the Program (or any work based on the
Program), the recipient automatically receives a license from the original
licensor to copy, distribute or modify the Program subject to these
terms and conditions. You may not impose any further restrictions on the
recipients' exercise of the rights granted herein.
7. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of the license which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
the license, you may choose any version ever published by the Free Software
Foundation.
8. If you wish to incorporate parts of the Program into other free
programs whose distribution conditions are different, write to the author
to ask for permission. For software which is copyrighted by the Free
Software Foundation, write to the Free Software Foundation; we sometimes
make exceptions for this. Our decision will be guided by the two goals
of preserving the free status of all derivatives of our free software and
of promoting the sharing and reuse of software generally.
NO WARRANTY
9. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
REPAIR OR CORRECTION.
10. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 1, or (at your option)
any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
Gnomovision version 69, Copyright (C) 19xx name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the
appropriate parts of the General Public License. Of course, the
commands you use may be called something other than `show w' and `show
c'; they could even be mouse-clicks or menu items--whatever suits your
program.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if
necessary. Here a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
program `Gnomovision' (a program to direct compilers to make passes
at assemblers) written by James Hacker.
<signature of Moe Ghoul>, 1 April 1989
Moe Ghoul, President of Vice
That's all there is to it!
--- The Perl Artistic License 1.0 ---
This software is Copyright (c) 1994 by Gisle Aas.
This is free software, licensed under:
The Perl Artistic License 1.0
The "Artistic License"
Preamble
The intent of this document is to state the conditions under which a
Package may be copied, such that the Copyright Holder maintains some
semblance of artistic control over the development of the package,
while giving the users of the package the right to use and distribute
the Package in a more-or-less customary fashion, plus the right to make
reasonable modifications.
Definitions:
"Package" refers to the collection of files distributed by the
Copyright Holder, and derivatives of that collection of files
created through textual modification.
"Standard Version" refers to such a Package if it has not been
modified, or has been modified in accordance with the wishes
of the Copyright Holder as specified below.
"Copyright Holder" is whoever is named in the copyright or
copyrights for the package.
"You" is you, if you're thinking about copying or distributing
this Package.
"Reasonable copying fee" is whatever you can justify on the
basis of media cost, duplication charges, time of people involved,
and so on. (You will not be required to justify it to the
Copyright Holder, but only to the computing community at large
as a market that must bear the fee.)
"Freely Available" means that no fee is charged for the item
itself, though there may be fees involved in handling the item.
It also means that recipients of the item may redistribute it
under the same conditions they received it.
1. You may make and give away verbatim copies of the source form of the
Standard Version of this Package without restriction, provided that you
duplicate all of the original copyright notices and associated disclaimers.
2. You may apply bug fixes, portability fixes and other modifications
derived from the Public Domain or from the Copyright Holder. A Package
modified in such a way shall still be considered the Standard Version.
3. You may otherwise modify your copy of this Package in any way, provided
that you insert a prominent notice in each changed file stating how and
when you changed that file, and provided that you do at least ONE of the
following:
a) place your modifications in the Public Domain or otherwise make them
Freely Available, such as by posting said modifications to Usenet or
an equivalent medium, or placing the modifications on a major archive
site such as uunet.uu.net, or by allowing the Copyright Holder to include
your modifications in the Standard Version of the Package.
b) use the modified Package only within your corporation or organization.
c) rename any non-standard executables so the names do not conflict
with standard executables, which must also be provided, and provide
a separate manual page for each non-standard executable that clearly
documents how it differs from the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
4. You may distribute the programs of this Package in object code or
executable form, provided that you do at least ONE of the following:
a) distribute a Standard Version of the executables and library files,
together with instructions (in the manual page or equivalent) on where
to get the Standard Version.
b) accompany the distribution with the machine-readable source of
the Package with your modifications.
c) give non-standard executables non-standard names, and clearly
document the differences in manual pages (or equivalent), together
with instructions on where to get the Standard Version.
d) make other distribution arrangements with the Copyright Holder.
5. You may charge a reasonable copying fee for any distribution of this
Package. You may charge any fee you choose for support of this
Package. You may not charge a fee for this Package itself. However,
you may distribute this Package in aggregate with other (possibly
commercial) programs as part of a larger (possibly commercial) software
distribution provided that you do not advertise this Package as a
product of your own. You may embed this Package's interpreter within
an executable of yours (by linking); this shall be construed as a mere
form of aggregation, provided that the complete Standard Version of the
interpreter is so embedded.
6. The scripts and library files supplied as input to or produced as
output from the programs of this Package do not automatically fall
under the copyright of this Package, but belong to whoever generated
them, and may be sold commercially, and may be aggregated with this
Package. If such scripts or library files are aggregated with this
Package via the so-called "undump" or "unexec" methods of producing a
binary executable image, then distribution of such an image shall
neither be construed as a distribution of this Package nor shall it
fall under the restrictions of Paragraphs 3 and 4, provided that you do
not represent such an executable image as a Standard Version of this
Package.
7. C subroutines (or comparably compiled subroutines in other
languages) supplied by you and linked into this Package in order to
emulate subroutines and variables of the language defined by this
Package shall not be considered part of this Package, but are the
equivalent of input as in Paragraph 6, provided these subroutines do
not change the language in any way that would cause it to fail the
regression tests for the language.
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is embedded; that is,
when no overt attempt is made to make this Package's interfaces visible
to the end user of the commercial distribution. Such use shall not be
construed as a distribution of this Package.
9. The name of the Copyright Holder may not be used to endorse or promote
products derived from this software without specific prior written permission.
10. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
The End

331
Agent-Windows/OGP64/usr/share/doc/perl-HTTP-Message/README.md Normal file
View file

@ -0,0 +1,331 @@
# NAME
HTTP::Message - HTTP style message (base class)
# VERSION
version 7.01
# SYNOPSIS
use parent 'HTTP::Message';
# DESCRIPTION
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](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
[does not currently](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 overrides the charset parameter for text content. The value
`none` can used to suppress decoding of the charset.
- `default_charset`
This overrides 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", "base64" and "br".
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](https://metacpan.org/pod/HTTP%3A%3AHeaders) 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
# AUTHOR
Gisle Aas <gisle@activestate.com>
# COPYRIGHT AND LICENSE
This software is copyright (c) 1994 by Gisle Aas.
This is free software; you can redistribute it and/or modify it under
the same terms as the Perl 5 programming language system itself.