libwww-perl / libwww-perl/Net-HTTP
t/live.t may fail
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 20
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
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.
Contributor guide
No contributing guide indexed for this repository
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
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.
Assessment
- Tech stack
- perl
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100