akka/akka-http

rejectEmptyResponse ends up with 405 instead of 404

Open

#1,473 opened on Oct 11, 2017

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import
1 - triagedhelp wantedt:docs

Description

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

Contributor guide

Tech stack
scala
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
ScalaAkka HTTP basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue reports that the `rejectEmptyResponse` directive returns a 405 status instead of 404 for certain HTTP methods. To investigate, look at the source code for `rejectEmptyResponse` in the Akka HTTP codebase, likely in the directives package. Check how it handles different HTTP methods and the logic for returning status codes. The example shows `get` and `delete` directives with `complete(StatusCodes.NoContent)`. The bug may be related to the order of directives or the method specific handling. Review the linked comments for any clues and consider testing with a minimal reproduction.