plug

Currently, you can only configure the unauthorised handler globally by setting it in config/*.exs files.

However, it makes sense to have the following scenario:

pipeline :api do
  plug Dictator, unauthorized_handler: JSONApiHandler
end

pipeline :browser do
  plug Dictator, unauthorized_handler: Render404HTML
end

We should add the unauthorized_handler to the opts

Apr	SEP	Nov
	02
2020	2021	2022

plug

Here are 259 public repositories matching this topic...

ueberauth / guardian

gf3 / dotfiles

mirego / elixir-boilerplate

dyanikoglu / ALS-Community

mutewinter / dot_vim

cpjk / canary

arithran / vim-pizza

whatyouhide / corsica

amilajack / eslint-plugin-flowtype-errors

hexedpackets / trot

poteto / terraform

absinthe-graphql / absinthe_plug

appsignal / appsignal-elixir

navinpeiris / logster

ajvondrak / remote_ip

heroku / plexy

tallarium / reverse_proxy_plug

bleacherreport / plug_logger_json

xiaweizi / flutter_weather_bg

kbrw / ewebmachine

cconstantin / plug_rails_cookie_session_store

sheharyarn / better_params

Nebo15 / multiverse

plugCubed / plugAPI

YinHangCode / homebridge-mi-outlet

subvisual / dictator

Allow the unauthorised handler to be configured when plugged

Add a handler for resources not found

nsweeting / authex

tompave / fun_with_flags_ui

plugCubed / plugCubed

imranismail / turbolinks.ex

Improve this page

Add this topic to your repo