dotnet/aspnetcore

Improve error messaging for 404s

Open

#5,350 opened on Oct 10, 2018

View on GitHubContributor guide
 (14 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
affected-fewarea-signalrenhancementfeature-client-javafeature-client-javascriptfeature-client-nethelp wantedseverity-nice-to-have

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

Usually a 404 occurs because sticky sessions are not enabled. We should provide a better error message here.

Contributor guide

Research direction
Locate the 404 error handling in the ASP.NET Core middleware and update the error message to mention sticky sessions.
Tech stack
csharp
Domain
backend
Issue type
Feature
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.
Under 1 hour
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
C#Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80