openresty / openresty/echo-nginx-module
content_handler should work also on TLS webserver
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 251
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 2
Description
consider this /echo.inc:
location {
default_type text/plain;
echo_duplicate 1 $echo_client_request_headers;
echo "\r";
echo_read_request_body;
echo_request_body;
echo_flush;
}
server {
listen *:80;
include /echo.inc;
}
server {
listen *:443 ssl http2;
ssl_certificate /cert.pem;
ssl_certificate_key /key.pem;
include /echo.inc;
}
the expected result happen only on port HTTP but not on HTTPS
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
Reproduce the issue with the shared /echo.inc configuration on the HTTP and HTTPS server blocks, comparing the response and request-body handling. Trace the echo module's content handling for TLS requests; done means the same expected result occurs on both ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, nginx
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100