In development I'm about to switch from the spray http client to akka-http's client - motivated by a customer stuck behind a https client-side proxy.
I've read through https://doc.akka.io/docs/akka-http/current/client-side/client-transport.html?language=scala , and think I get it. However, I have some one big concern about what I'm reading. "Right now, configuration is only possible with code (and not through config files)." Spray had config values in place for both HTTP and HTTPS client -side proxies, and would fall back to the JVM's values for an HTTP client-side proxy. (The Spray HTTPS proxy support was not implemented before the end of the project.) Is there some reason the code does not use (or fall back to) the default JVM settings for the HTTPS client-side proxy? (The example code, by the way, looks fantastic.) Thanks, David -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
