dimitarvp

dimitarvp

I’m looking into returning JSON errors from an API app. I know the specs dictate you must always return HTML on certain error codes but I want to circumvent that because I’ll have complete control both on the calling side and the service itself. Plus the service will send logs and telemetry and I want errors to be machine-parseable.

I tried a few things after searching the forum but I couldn’t manage to make any of them work.

Then I stumbled upon Plug.ErrorHandler — Plug v1.20.2. Call me stupid but I have no clue how to use it?

So as a start I want all 404s and 500s to be wrapped with a JSON key errors in an object, returned alongside a 404 and 500 status.

Is this possible using Plug.ErrorHandler? If so, how exactly?

Showing Posts 1 to 7

Exadra37

Exadra37

Please bear in mind that all what I am about to suggest is from the top of my mind, therefore not tested, and may be wrong, but hey it doesn’t hurt for you to give it a try :slight_smile:

  def handle_errors(conn, %{kind: _kind, reason: _reason, stack: _stack}) do
    send_resp(conn, conn.status, "Something went wrong")
  end

If I am not mistake the above will override the call to the Error view at lib/yourapp_web/views/error_view.ex.

I think that this will return it in json:

# You may need to use the Jason library if returning only the map doesn't work.
# You also want to put the `application/json` header in the `conn`
send_resp(conn, conn.status,%{error: conn.status, message:  "Something went wrong"})

Maybe you can simplify the above to use in your router:

# file: lib/yourapp_web/router.ex
  pipeline :api do
    plug :accepts, ["json"],
    plug :handle_errors
  end

  # you may need to pattern match in `conn.status` to make this work
  def handle_errors(conn, %{kind: _kind, reason: _reason, stack: _stack}) do
    # You may need to use the Jason library if returning only the map doesn't work.
    # You also want to put the `application/json` header in the `conn`
    send_resp(conn, conn.status,%{error: conn.status, message:  "Something went wrong"})
  end

EDIT: On a second though I think this isn’t reflecting the intended use from the Plug.ErrorHandler

An Alternative that you can try is to change the Error view to always return a JSON object:

defmodule YourAppWeb.ErrorView do
  use YourAppWeb, :view

  require Logger

  # If you want to customize a particular status code
  # for a certain format, you may uncomment below.
  def render(template, assigns) do
    _json_error(template, assigns)
  end

  # By default, Phoenix returns the status message from
  # the template name. For example, "404.html" becomes
  # "Not Found".
  def template_not_found(template, assigns) do
    _json_error(template, assigns)
  end

  defp _json_error(template, assigns) do

    Logger.info("Error template: #{template}")
    # render("500.html", assigns)
    
    # I am not sure, but I think you can just return a Map, otherwise just try to use the Jason library.
    %{
      error: 400, # You need to extract it from assigns or template name
      maessage: "Whoops!"
    }

  end
  
end
dimitarvp

dimitarvp OP

I still don’t understand where to put this copy-pasted module code in my Phoenix project, and how do I register it to be used – in the router, the endpoint, somewhere else?

The docs kind of assume certain knowledge that I found I don’t have.

Exadra37

Exadra37

I update my previous post while you made this one to make it clear, but here it his again:

# file: lib/yourapp_web/router.ex
  pipeline :api do
    plug :accepts, ["json"],
    plug :handle_errors
  end

  # you may need to pattern match in `conn.status` to make this work
  def handle_errors(conn, %{kind: _kind, reason: _reason, stack: _stack}) do
    # You may need to use the Jason library if returning only the map doesn't work.
    # You also want to put the `application/json` header in the `conn`
    send_resp(conn, conn.status,%{error: conn.status, message:  "Something went wrong"})
  end

This is a guess from me, not actually tried it.

EDIT: On a second though I think this isn’t reflecting the intended use from the Plug.ErrorHandler

dimitarvp

dimitarvp OP

Nope, that didn’t work. :expressionless:

Hitting a non-existent endpoint with curl:

HTTP/1.1 404 Not Found
cache-control: max-age=0, private, must-revalidate
content-length: 1333
content-type: text/markdown; charset=utf-8
date: Mon, 12 Apr 2021 16:33:02 GMT
server: Cowboy

# Phoenix.Router.NoRouteError at POST /does_not_exist

Exception:

    ** (Phoenix.Router.NoRouteError) no route found for POST /does_not_exist (MyAppWeb.Router)
# <snip>

And it’s returning markdown text? Why?

I am still trying to understand how do I just intercept ALL errors and wrap them in keys in a resulting JSON object.

Exadra37

Exadra37

Sorry for not having given you a good solution :frowning:

But did you try the Error view approach? I think that one should work :thinking:

Because you are in development mode. Go to config/dev.exs and set debug_errors to false.

dimitarvp

dimitarvp OP

No idea what to do exactly there either. :003:

It’s been an absolutely awful day and I’d love complete code examples. At least today. If not, I’ll try formulating a solution on a fresh head tomorrow. :smiley:

Exadra37

Exadra37

I showed it to you in my first post:

This file can be found in your app web views folder.

Basically ti’s overriding the render/2 function called to render the error templates for each error status code that is defined in the templates folder.

It also customizes the template_not_found/2 to return the Json error.

— All posts loaded —

Where Next? Top

Trending in Questions Top

water
I’m aware of 2 such projects, are there others? git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
katta
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
peck
Hi everyone. My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
bradley
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
unaware8150
Hello folks! So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Alvinkariuki
How Can I Optimise Compile Time Dependencies I have been building an elixir application for about 2 years now. Many modules and files ha...
New
leoschweizer
Hi, we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New

Other Trending Topics Top

KristerV
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
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
budgie
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with. But I don’t use it anymore. Serverless was the promis...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews