Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

t/live.t may fail

Open
#87 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
perl
Domain
testing

Research direction

Start with t/live.t and reproduce the periodic failure against example.com if possible. Review the suggested gstatic URLs and the AUTHOR_TESTING or RELEASE_TESTING option, then make the test use a reliable configuration and confirm the live test no longer fails because of the reported 403 or 502 responses.

Written by the indexing model from the issue text.

Description

example.com seems to fail periodically with:

--2025-11-08 10:12:55-- http://www.example.com/
Resolving www.example.com (www.example.com)... 66.96.160.151
Connecting to www.example.com (www.example.com)|66.96.160.151|:80... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2025-11-08 10:12:55 ERROR 502: Bad Gateway.

--2025-11-08 10:12:49-- http://example.com/
Resolving example.com (example.com)... 66.96.160.151
Connecting to example.com (example.com)|66.96.160.151|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2025-11-08 10:12:49 ERROR 403: Forbidden.

You might want to reconfigure the test for http://www.gstatic.com/generate_204 or http://www.gstatic.com/robots.txt or change this to AUTHOR_TESTING or RELEASE_TESTING

There might be a html page available at http://www.gstatic.com/ but I don't know of one.

Dominant language
Perl
Stars
20
Forks
27
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from libwww-perl/Net-HTTP

All issues in libwww-perl/Net-HTTP

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.