openresty / openresty/test-nginx
udp_listen socket is shut down after response
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 456
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Description
From what i gather after responding the given udp_reply, socket is closed. Is this intentional ?
It is very useful in pipelined_requests to use the udp servers upon each request.
Maybe this could be implemented as that same response is given on every request or better yet multiple responses could be defined !
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 udp_listen and udp_reply handling used by pipelined_requests, then trace when the UDP socket is shut down after a response. Check existing tests for repeated requests and define coverage for keeping the socket available or supporting multiple responses. Done means the intended lifecycle is implemented and verified by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100