I am moving from spray to akka-http and I am looking at a subtle but bewildering change regarding the Content-Type in HttpRequest.
In spray, it looked like this HttpRequest(PUT,http://localhost:8080/mybucket1/,List(Host: localhost:8080, Authorization: AWS BCDEFGHIJKLMNOPQRSTA:LLUwDm85x8uWBWsu4Vgx8FK1Hec=, User-Agent: aws-sdk-java/1.10.12 Mac_OS_X/10.10 Java_HotSpot(TM)_64-Bit_Server_VM/25.45-b02/1.8.0_45, Date: Tue, 03 Nov 2015 08:46:17 GMT, Content-Type: application/x-www-form-urlencoded; charset=UTF-8, Content-Length: 0, Connection: Keep-Alive),Empty,HTTP/1.1) But in akka-http, the same request in client-side reached to server looks different (port number changed). The request is made by aws-sdk-java of the same version that makes a bucket "mybucket1". HttpRequest(HttpMethod(PUT),http://localhost:9000/mybucket1/,List(Host: localhost:9000, authorization: AWS BCDEFGHIJKLMNOPQRSTA:j8581UwAQuUcIbJ109TfpUZCNMk=, user-agent: aws-sdk-java/1.10.12 Mac_OS_X/10.10 Java_HotSpot(TM)_64-Bit_Server_VM/25.45-b02/1.8.0_45, Date: Tue, 03 Nov 2015 08:38:24 GMT, Connection: Keep-Alive),HttpEntity.Strict(application/x-www-form-urlencoded; charset=UTF-8,ByteString()),HttpProtocol(HTTP/1.1)) You can see that Content-Type moved from header list to HttpEntity. Is this intended so Content-Type is modeled into HttpEntity in both HttpRequest and HttpResponse? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
