Akka HTTP configuration details exposed to client on EntityStreamSizeException · akka/akka-http#1015

(7 留言) (0 反應) (1 負責人)Scala (1,311 star) (598 fork)batch import

3 - in progressbughelp wantedt:core

描述

Hi,

The current implementation of the EntityStreamSizeException handling exposes a detailed message about which Akka settings to use (to allow bigger contents in requests) to the client, even though verbose-error-messages is set to off.

I changed the Class to extend ExceptionWithErrorInfo to distinguish between a summary and a detailed message. There is a check for the verbosity setting in HttpServerBluePrint:459 but it seems like it is never called and the ErrorInfo.formatPretty result is returned to the client (which may also just be the result of RuntimeException.getMessage as ExceptionWithErrorInfo extends RuntimeException).

Do you have an idea why or what to change to only display the summary in that case? The mentioned classes are in the akka-http-core module.

You can trigger it by setting akka.http.server.parsing.max-content-length to 1 and send some data with your request.

I pushed my current changes to https://github.com/makubi/akka-http/commit/546af4fa4ac4c5c7e78df2c8b3ba083aa64b3c2e.

Thanks in advance.

貢獻者指南

技術棧: scala
領域: backendsecurity
議題類型: bug
難度: 3
預計時間: half day
活動狀態: stale
清晰度: clear
前置要求: ScalaAkka HTTP error handling
新手友善度: 45
研究方向: Investigate the current implementation of EntityStreamSizeException in ErrorInfo.scala (line 83) and its usage in HttpServerBluePrint.scala (line 459). The reporter has proposed modifying EntityStreamSizeException to extend ExceptionWithErrorInfo to separate summary and detail. Check why the verbosity check in HttpServerBluePrint is not triggered and ensure that only the summary is exposed when verbose error messages is off. Review the linked commit (546af4fa4ac4c5c7e78df2c8b3ba083aa64b3c2e) for reference.