envoyproxy/envoy

Unicode handling

Open

#13,358 opened on Oct 1, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/docsarea/httpenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Document how Envoy support Unicode and develop a policy for testing to ensure we have sufficient coverage to convince ourselves that we do the right thing. There are well known places where we do not do explicit Unicode handling, e.g. in path normalization today, this needs to be cleanly communicated in docs etc.

Contributor guide

Research direction
Identify areas in Envoy where Unicode handling is implicit or missing, such as path normalization, and propose documentation and a testing policy.
Tech stack
cpp
Domain
backendinfrastructure
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gitbasic understanding of Envoy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60