@gitleet No, but it looks like you're on MacOS. Perhaps someone else could try and see if it's a problem there.
@GrafBlutwurst Blaze does not support proxies, though there's a dated, half-baked PR for it. AHC definitely supports it. I think everything but Blaze and maybe Ember do. All of the other backends delegate to other backends instead of being from scratch, and would get their proxy support through that.
@Taig It's CPU bound, so if you use
global for your CPU-bound work, it's a good choice. A fixed pool is theoretically better. I've never measured a significant win, but Daniel Spiewak has measured dramatic wins in other contexts, and has good theoretical justification for it.
Exposing that parameter has caused a lot of confusion, and it's regrettable that it's there at all: it leaks an implementation detail of blaze. The reason we don't default it to global is that a lot of cats-effect apps carefully avoid initializing the global pool. But if that doesn't bother you, it's probably a fine choice.
@rossabaker yeah i am playing with AHC now and it works-ish I am actually hitting this particular isseus (but only in testing, it seems to work fine when i just deploy the service and work with it) http4s/http4s#3527 I'm currenlty throwing ideas at the proverbial wall and see what sticks to figure out what is causing this
I have been one of the leading whiners about them on the phone, and blindly did it in the browser.
@GrafBlutwurst If you are still looking for a backend with proxy support: https://jdk-http-client.http4s.org/stable/#custom-clients
If the JDK11 requirement doesn't bother you, that one ticks most of the rest of the boxes.
I think I've been furiously treading water just reviewing all the (good!) PRs.
With smaller payloads (like 3kb payloads), the https connection stays alive and is re-usable for the next https call. With larger payloads, the connection is being shutdown by http4s client.
Is there a solution for doing more advanced form data parsing in http4s like this former decoder in Play https://www.playframework.com/documentation/2.8.x/ScalaForms?
@vmanpuria That seems like perhaps an idle timeout bug. If you could create an issue with the logs on highest level when it occurs we can try to figure out what's killing the connection.
@ChristopherDavenport I'll take another look at UrlForm I thought all it can do is to parse the body to
Here is an example of more advanced decoder in play, the
Map[String, Chain[String]].Here is an example of more advanced decoder in play, the
Form in play can decode into ADTs like thisval userFormNested: Form[UserAddressData] = Form(
mapping(
"name" -> text,
"address" -> mapping(
"street" -> text,
"city" -> text
)(AddressData.apply)(AddressData.unapply)
)(UserAddressData.apply)(UserAddressData.unapply)
)
I am making a very simple webserver, and I am getting a CORS issue on the browser, while making a GET request from ajax
I have did this but no luck:
HttpRoutes.of[IO] {
case GET -> Root / "employees" =>
try {
val answer = queries.getEmployees
Ok(Json.obj(("employees", answer.map(_.asJson).asJson)))
.map(_.putHeaders(Header("Origin", "*")))
}
But the examples are valid only if making the requests from http4s itself
My service kickstarter looks like this:
def stream(managementRoutes: ManagementRoutes)(implicit T: Timer[IO], C: ContextShift[IO]): Stream[IO, Nothing] = {
for {
_ <- BlazeClientBuilder[IO](global).stream
service = managementRoutes.getTransportInformation
corsService = CORS(service, methodConfig)
httpApp = corsService.orNotFound
finalHttpApp = Logger.httpApp(true, true)(httpApp)
exitCode <- BlazeServerBuilder[IO](global)
.bindHttp(8080, "0.0.0.0")
.withHttpApp(finalHttpApp)
.serve
} yield exitCode
}.drain
3 replies
with
private val methodConfig = CORSConfig(
anyOrigin = true,
anyMethod = false,
allowedMethods = Some(Set("GET", "POST")),
allowCredentials = true,
maxAge = 1.day.toSeconds)
and then my end point routes are:
HttpRoutes.of[IO] {
case GET -> Root / "employees" =>
try {
val answer = queries.getEmployees
Ok(Json.obj(("employees", answer.map(_.asJson).asJson)))
.map(_.putHeaders(Header("Origin", "localhost")))
}
catch {
case e: Throwable =>
println(e.getMessage)
InternalServerError(s"Something went wrong:\n${e.getMessage}")
}
and I get
Access to XMLHttpRequest at 'localhost:8080/employees' from origin 'http://localhost:63342' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, chrome-extension, edge, https.
So I used middleware to start the service with cors configuration, and added the Origin header response in my
/employees route
$(document).ready(function(){
$.ajax({
url: 'localhost:8080/employees',
type: 'GET',
success: function (response) {
console.log("Hello");
console.log(response);
var trHTML = '';
$.each(response, function (i, employee) {
trHTML += '<tr><td>' + employee.name + '</td><td>' + employee.created + '</td><td>' + employee.modified + '</td></tr>';
});
$('#employees').append(trHTML);
},
error: function (xhr, status, error) {
console.log(xhr.status);
console.log(xhr.statusText);
}
});
});
Sorry to ask something I think must have been asked before, but I seem unable to google it. I've got a play JSON
JsValue that I want to POST with an http4s Client the first stumbling block is that it seems impossible to figure out what POST accepts as parameters in this example, it's so obfuscated that I don't seem to be able to find it and neither can IntelliJ!
Do I have to use circe to convert it? I'd rather just chuck it in as a string with a json content-type tbh if that's the case
Oop, found an old project where i'd done it. I needed this custom dsl for monix Task:
object task extends Http4sClientDsl[Task]
and:import org.http4s.play._
from: "org.http4s" %% "http4s-play-json" % http4sVersion,
I couldn't find anything in the docs on how to do this
