libwww-perl / libwww-perl/HTTP-Daemon
[PATCH] Documentation - content-type header [rt.cpan.org #82313]
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 6
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Migrated from rt.cpan.org#82313 (status was 'open')
Requestors:
- andy@andybev.com
Attachments:
From andy@andybev.com on 2012-12-29 00:39:22
:
Could I suggest the attached patch for the documentation please? I spent
a while searching the internet for the best way to add a content-type
header; seeing as everyone will almost certainly want to do this, I
think an example would be good in the main documentation.
Many thanks.
From andy@andybev.com on 2014-12-29 14:31:52
:
Is there any chance of getting this fixed please? It's preventing
automatic building with Debian, as debhelper appears to use
-Werror=format-security by default, which forces the build to fail with
this potential security problem highlighted.
Thanks!
From andy@andybev.com on 2014-12-29 14:37:06
:
Sorry, ignore that, sent to the wrong bug number...
From srezic@cpan.org on 2015-02-11 11:52:45
:
On 2012-12-28 19:39:22, abeverley wrote:
> Could I suggest the attached patch for the documentation please? I spent
> a while searching the internet for the best way to add a content-type
> header; seeing as everyone will almost certainly want to do this, I
> think an example would be good in the main documentation.
It looks like this issue should be migrated to https://rt.cpan.org/Dist/Display.html?Name=HTTP-Daemon
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the attached content.patch and identify the main documentation file it targets. Confirm that the request has not moved to the HTTP-Daemon distribution referenced in the thread, then update the documentation with the content-type header example; done means the example is present and the documentation remains accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100