Protocol-HTTP 1.0.7
- Released by
- DMOL
- Version
- Release Date
- 2020-06-22
- Kwalitee
- 140.62
- Core Kwalitee
- 90.62
- LINKS
Protocol-HTTP 1.0.7
Kwalitee Issues
- has_readme
-
Add a README to the distribution. It should contain a quick description of your module and how to install it.
- manifest_matches_dist
-
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
Error:
- MANIFEST (151) does not match dist (149):
- Missing in Dist: Protocol-HTTP-1.0.7/META.json, Protocol-HTTP-1.0.7/META.yml
- use_strict
-
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Error: Protocol::HTTP::Compression, Protocol::HTTP::Cookiejar, Protocol::HTTP::Error, Protocol::HTTP::Message, Protocol::HTTP::Request, Protocol::HTTP::RequestParser, Protocol::HTTP::Response, Protocol::HTTP::ResponseParser
- meta_yml_declares_perl_version
-
If you are using Build.PL define the {requires}{perl} = VERSION field. If you are using MakeMaker (Makefile.PL) you should upgrade ExtUtils::MakeMaker to 6.48 and use MIN_PERL_VERSION parameter. Perl::MinimumVersion can help you determine which version of Perl your module needs.
- meta_yml_has_license
-
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
- use_warnings
-
Add 'use warnings' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
Error: Protocol::HTTP, Protocol::HTTP::Compression, Protocol::HTTP::Cookiejar, Protocol::HTTP::Error, Protocol::HTTP::Message, Protocol::HTTP::Request, Protocol::HTTP::RequestParser, Protocol::HTTP::Response, Protocol::HTTP::ResponseParser
- meta_yml_has_provides
-
Add all modules contained in this distribution to the META.yml field 'provides'. Module::Build or Dist::Zilla::Plugin::MetaProvides do this automatically for you.
- meta_yml_has_repository_resource
-
Add a 'repository' resource to the META.yml via 'meta_add' accessor (for Module::Build) or META_ADD parameter (for ExtUtils::MakeMaker).
- has_separate_license_file
-
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.
Modules
| Name | Abstract | Version | View |
|---|---|---|---|
| Protocol::HTTP | very fast HTTP protocol incremental parser and serializer | 1.000007 | metacpan |
| Protocol::HTTP::Compression | HTTP parser compression constants | metacpan | |
| Protocol::HTTP::Error | HTTP parser error constants | metacpan | |
| Protocol::HTTP::Message | base class for HTTP request and response | metacpan | |
| Protocol::HTTP::Request | HTTP request class | metacpan | |
| Protocol::HTTP::RequestParser | HTTP request parser | metacpan | |
| Protocol::HTTP::Response | HTTP response class | metacpan | |
| Protocol::HTTP::ResponseParser | HTTP response parser | metacpan |
Provides
| Name | File | View |
|---|---|---|
| Protocol::HTTP::CookieJar | lib/Protocol/HTTP/Cookiejar.pm | metacpan |