Valid Content-Type header are eaten-up by headerValueByName directive · akka/akka-http#1011

(3 comments) (0 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import

1 - triagedhelp wantedt:docst:routing

Description

It seems that HeaderValueByName, optinalHeaderValueByName and headerValueByType are not returning the content type if it is an valid one.

I posted already something on the mailing list https://groups.google.com/forum/#!topic/akka-user/ZClckCsc8e4

For testing purpose I wrote a small server (to test my client) object WebServer extends HttpApp { def route: Route = path("publishvalid") { optionalHeaderValueByName("Content-Type") { header => println("Content-Type is "+header) post { complete("") } } } }

While doing this I observed that the directive optionalHeaderValueByName was never returning a valid value if the Content-Type I send was valid (I used postman for it). If I used a customized Content-Type it works fine. Observed the same fore headerValueByName and HeaderContentType.

This seems like an bug for me, evenso it is mentioned here http://doc.akka.io/docs/akka-http/10.0.4/scala/http/common/http-model.html#http-model that the Content-Type is treated differntly.

Regards

Wolfgang

Contributor guide

Tech stack: None
Domain: backend
Issue type: bug
Difficulty: 3
Estimated time: 1-3 hours
Activity status: stale
Clarity: mostly clear
Prerequisites: basic understanding of Akka HTTPknowledge of Scala
Newbie friendliness: 30
Research direction: Investigate the implementation of headerValueByName and optionalHeaderValueByName directives in the Akka HTTP source code, specifically how they handle the Content Type header. Note that the HTTP model treats Content Type specially, as mentioned in the docs. Look at the model's internal representation to understand why valid Content Type values are not returned, while custom values work. Check for any filtering or transformation of the Content Type header before it reaches the directive.