spinframework / spinframework/spin
Mistakenly using `https` on outbound HTTP request results in hard-to-debug error
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
I sent an outbound HTTP request to https://localhost:3001/ when I meant to write http://localhost:3001/. It failed with just RequestError. There was nothing in the error or in Spin logs. In the end I had to hack a println! into the Spin source to figure out what was going on. This is a suboptimal diagnostic experience.
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
Start by reproducing the outbound request to https://localhost:3001/ when the service only speaks HTTP, then trace the RequestError path and Spin logs; the issue names no source file or test. Done means the protocol mismatch produces a useful diagnostic in the error or logs instead of only RequestError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100