ndrean
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?
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
Hi everyone,
I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding.
I sta...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Is there any way to avoid the Hologram compiler running when using iex? It seems like the front-end code could potentially be disregarded...
New
** (ArgumentError) expected :max_attempts to be a positive integer, got: {:@, [line: 10, column: 19], [{:max_attempts, [line: 10, column:...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex











First Post!- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
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
Thanks for taking a look. Yes, it may seem dumb but I realised afterwards that the method
chunkwas sending a response and setting theconn.stateto:setso 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 thechunkfrom this POST request handler, pubsub the payload, and a GET endpoint has areceive dothat emits the payload through SSE.