getWWW problems
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
1. If the return code is not 200 (e.g. 300 for redirect or 400 for errors) the function should throw an error object with information (absorbing #663)
2. It should work with `https://`!!
3. Perhaps it should work with `file://` as well?
Maybe let's just replace it with something modern that supports different protocols.
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 by locating the getWWW entry point and inspect how it handles response codes and URL protocols. Define the supported behavior for non-200 responses, https://, and possibly file://, then verify that errors include useful information and that the selected protocols work as intended.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100