dotnet/aspnetcore

Review and update form parsing logic

Open

#2,733 建立於 2018年1月2日

在 GitHub 查看
 (7 留言) (0 反應) (0 負責人)C# (37,933 star) (10,653 fork)batch import
affected-very-fewarea-networkingbugfeature-http-abstractionshelp wantedseverity-nice-to-have

描述

From @Tratcher on Tuesday, August 26, 2014 12:32:12 PM

src/Microsoft.AspNet.WebUtilities/ParsingHelpers.cs has at least one place where it calls char.IsWhiteSpace, but this allows many strange Unicode characters. Review this parsing code and update it to be more accurate.

Copied from original issue: aspnet/HttpAbstractions#119

貢獻者指南

技術棧
csharp
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
understanding of Unicode character classificationsfamiliarity with ASP.NET Core codebase
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
The issue points to src/Microsoft.AspNet.WebUtilities/ParsingHelpers.cs where char.IsWhiteSpace is used. Research which Unicode whitespace characters are valid in form parsing (e.g., RFC 1866) and propose a constrained set. Check if the issue is still relevant given the repo's age; the file path may have changed in the current dotnet/aspnetcore tree. No linked PRs or assignees exist, so the fix is open.