Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

content_handler should work also on TLS webserver

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, nginx
Domain
backend

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.

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

Dominant language
C
Stars
1.2k
Forks
250
Avg merge
25m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openresty/echo-nginx-module

All issues in openresty/echo-nginx-module

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.