tjstankus
I’ve got code to verify webhook signatures that’s similar to the code examples in this Dashbit article. In the dev environment, it works fine - the request body is read into conn.assigns[:raw_body]. In the test environment, however, the custom body_reader isn’t being called; the request body is not read into assigns.
Has anyone seen something like this or have some ideas? I’ve found similar posts related to Plug.Parsers and custom body_reader, but nothing specifically about testing differences. I’ve tried a number of things with Plug.Conn in the test environment, to no avail so far. Thanks!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
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
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
Are you sure whatever you do in your tests does actually hit
Plug.Parsers? Can you show your setup?tjstankus
In dev, an
IO.putsfrom inside the function called byPlug.Parsersbody_readergets written to stdout. In test, it does not, andconn.assignsis an empty map instead of containing the request body, as it does in dev. Since this is a proprietary app, I’ll see if I can replicate the problem in a minimal Phoenix app and share that code here.voltone
Make sure you pass in the request body as a string inside your tests. If you pass in a map, Plug takes some shortcuts that bypass Plug.Parsers
tjstankus
Thank you @voltone and @LostKobrakai for your responses. I didn’t realize
Plug.Parserswas being bypassed by design. Got it working byposting the body as a JSON encoded string.pmargreff
I just hit the same wall, and it was a surprise, mainly because this is not something explicit as most things from Plug/Phoenix.
Where is the best place to document that? Adding a note to
Plug.Parserenough or it’s a broader thing that should be highlighted elsewhere?