rejectEmptyResponse ends up with 405 instead of 404

Repository metrics

Stars

1,311 stars (1,311 stars)

PR merge metrics

Avg merge 1d 10h (Avg merge 1d 10h)2 merged PRs in 30d (2 merged PRs in 30d)

Description

    rejectEmptyResponse {
      get {
        complete(StatusCodes.NoContent)
      }
    } ~ delete {
      complete(StatusCodes.NoContent)
    }

Contributor guide

Research direction

Examine the implementation of rejectEmptyResponse directive and trace how the HTTP method validation leads to 405 instead of 404.

Tech stack

None

Domain

backend

Issue type

Bug

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

ScalaAkka HTTP

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70