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’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
I’m new to elixir and just tried to install the elixirLS extension for VScode(ium) and it is throwing some errors that I would like help ...
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
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
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
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex











Showing Posts 1 to 2- 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?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.