ndrean

ndrean

Plug.Conn: response back from post

I have an Elixir server and I “post” some data to an endpoint in order to broadcast this data with SSE. For the moment, I haven’t connected the front-end to check, only testing with curlin the terminal. I am surprised to get back the message I am posting and can’t just set a response like “ok”.

I do:

curl -X POST -H "content-type: application/json" -d '{"test": "hello"}' https://localhost:4000/post
# -> response:
event: message
data: {"test":  "hello"}

The following Plug server is started by the app supervisor ({Plug.Cowboy, scheme: :http, plug: My.Router, options: plug_options}):

defmodule My.Router do
  import Plug.Conn
  use Plug.Router

  plug(:match)
  plug(Plug.Parsers, parsers: [:json], pass: ["text/*", "application/json"], json_decoder: Jason)
  plug(:dispatch)

  post "/post" do
    data = Jason.encode!(conn.params)
    msg = "event: message\ndata: #{data}\n\n"

    conn =
      conn
      |> put_resp_header("connection", "keep-alive")
      |> put_resp_header("content-type", "text/event-stream")
      |> send_chunked(200)

    {:ok, conn} = chunk(conn, msg)
    conn
  end

It is useless to get the message back. Furthermore, I can’t do something like send_resp(conn, 200, :ok) as I get an error message saying that the response was already sent.
Any experience?

First Post!

al2o3cr

al2o3cr

The output from curl there looks like the server-sent event content you requested be sent by calling chunk(conn, msg); what else did you expect to happen?

Last Post!

ndrean

ndrean

Thanks for taking a look. Yes, it may seem dumb but I realised afterwards that the method chunk was sending a response and setting the conn.state to :set so I could not send an appropriate response afterwards. I wanted a standard response as found in the doc of the Plug middleware: conn |> resp(200, "broadcasted") |> send_resp(). So it was just wrong. I removed the chunk from this POST request handler, pubsub the payload, and a GET endpoint has a receive do that emits the payload through SSE.

Where Next?

Popular in Questions Top

vegabook
I’m brand new to Phoenix and I have stripped one of the demo applications to the bone. I just want to get an svg up on the screen. Here i...
New
jononomo
I am trying to figure out how Mix knows whether the environment is test, dev, or prod – where is this set? Thanks.
New
Qqwy
Original source of discussion: This topic on the Pragmatic Programmers’ Functional Web Development with Elixir, OTP, and Phoenix forum. ...
New
jerry
Good day to you all. I have been struggling to get a query involving like and ilike to work. Can anyone assist me on this, please? pro...
New
siddhant3030
Hi, I have to write a raw query for one of my project. But till now I have used ecto queries and don’t have much experience writing raw ...
New
Harrisonl
We have an ECS cluster with 4 services, where each task joins a single cluster, via discovery ECS discovery service. Currently when I de...
New
senggen
Erlang/OTP 25 [erts-13.2.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] 15:22:35.803 [error] gen_event {lager_file_backend...
New

Other popular topics Top

minhajuddin
I have seen a lot of code which picks the first element from a list using Enum.at(0) instead of List.first. Is there a reason why people ...
New
grych
Hi folks, Few months ago I have announced the proof-of-concept of the library to manipulate the browsers DOM objects directly from Elixi...
639 54260 488
New
Qqwy
Original source of discussion: This topic on the Pragmatic Programmers’ Functional Web Development with Elixir, OTP, and Phoenix forum. ...
New
greenz1
I have a phoenix application from which a user can download multiple(5-6) files of size 1MB. I couldn’t find anything related to sending ...
New
axelson
This post is a wiki (feel free to hit the edit button near the bottom right of this post to add your own changes!) This post collects co...
239 49266 226
New
Harrisonl
We have an ECS cluster with 4 services, where each task joins a single cluster, via discovery ECS discovery service. Currently when I de...
New

We're in Beta

About us Mission Statement